[Desktop-packages] [Bug 1841953] Re: Bionic ⋅ SuperTuxKart ⋅ Flickering shadows ⋅ Haswell i915
ok, thanks then this needs to be filed upstream at gitlab.freedesktop.org/mesa ** Changed in: mesa (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1841953 Title: Bionic ⋅ SuperTuxKart ⋅ Flickering shadows ⋅ Haswell i915 Status in mesa package in Ubuntu: Confirmed Status in supertuxkart package in Ubuntu: New Bug description: Hi, for few weeks now, I've noticed a big change in graphic performance while playing famous SuperTuxKart on ubuntu bionic : shadows are flickering, all over the screen, it's a big pain for eyes ( and wonder what would happen for epileptic people ). My computer is : Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz with 16Go ram and Haswell integrated graphics. coeur-noir@asgard:~$ lspci -k | grep -A 2 -i "VGA" 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller (rev 06) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller Kernel driver in use: i915 coeur-noir@asgard:~$ sudo lshw -c video *-display description: VGA compatible controller produit: Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller fabriquant: Intel Corporation identifiant matériel: 2 information bus: pci@:00:02.0 version: 06 bits: 64 bits horloge: 33MHz fonctionnalités: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 ressources: irq:26 mémoire:f780-f7bf mémoire:e000-efff portE/S:f000(taille=64) mémoire:c-d coeur-noir@asgard:~$ My Ubuntu Budgie 18.04 is : coeur-noir@asgard:~$ lsb_release -rd Description: Ubuntu 18.04.3 LTS Release: 18.04 coeur-noir@asgard:~$ uname -a Linux asgard 5.0.0-23-generic #24~18.04.1-Ubuntu SMP Mon Jul 29 16:12:28 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux coeur-noir@asgard:~$ mesa packages are : coeur-noir@asgard:~$ dpkg -l | grep mesa ii libegl-mesa0:amd64 19.0.8-0ubuntu0~18.04.1 amd64free implementation of the EGL API -- Mesa vendor library ii libegl1-mesa:amd64 19.0.8-0ubuntu0~18.04.1 amd64transitional dummy package ii libgl1-mesa-dri:amd64 19.0.8-0ubuntu0~18.04.1 amd64free implementation of the OpenGL API -- DRI modules ii libgl1-mesa-dri:i38619.0.8-0ubuntu0~18.04.1 i386 free implementation of the OpenGL API -- DRI modules ii libgl1-mesa-glx:amd64 19.0.8-0ubuntu0~18.04.1 amd64transitional dummy package ii libgl1-mesa-glx:i38619.0.8-0ubuntu0~18.04.1 i386 transitional dummy package ii libglapi-mesa:amd64 19.0.8-0ubuntu0~18.04.1 amd64free implementation of the GL API -- shared library ii libglapi-mesa:i386 19.0.8-0ubuntu0~18.04.1 i386 free implementation of the GL API -- shared library ii libgles2-mesa:amd64 19.0.8-0ubuntu0~18.04.1 amd64transitional dummy package ii libglu1-mesa:amd64 9.0.0-2.1build1 amd64Mesa OpenGL utility library (GLU) ii libglu1-mesa:i386 9.0.0-2.1build1 i386 Mesa OpenGL utility library (GLU) ii libglx-mesa0:amd64 19.0.8-0ubuntu0~18.04.1 amd64free implementation of the OpenGL API -- GLX vendor library ii libglx-mesa0:i386 19.0.8-0ubuntu0~18.04.1 i386 free implementation of the OpenGL API -- GLX vendor library ii libosmesa6:amd6419.0.8-0ubuntu0~18.04.1 amd64Mesa Off-screen rendering extension ii libosmesa6:i386 19.0.8-0ubuntu0~18.04.1 i386 Mesa Off-screen rendering extension ii libwayland-egl1-mesa:amd64 19.0.8-0ubuntu0~18.04.1 amd64transitional dummy package ii mesa-utils 8.4.0-1 amd64Miscellaneous Mesa GL utilities ii mesa-utils-extra8.4.0-1 amd64Miscellaneous Mesa utilies (opengles, egl) ii mesa-va-drivers:amd64 19.0.8-0ubuntu0~18.04.1 amd64Mesa VA-API video
[Desktop-packages] [Bug 1847980] Re: Lightdm is just a black screen when booting kernel 5.3 on an i5-6500, but kernels 5.0/5.2 work
great, then try 5.4-rc1 hoping that it's broken there, then a fix would be fairly easy to spot -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1847980 Title: Lightdm is just a black screen when booting kernel 5.3 on an i5-6500, but kernels 5.0/5.2 work Status in lightdm package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: Xorg freeze at boot on Intel Corporation HD Graphics 530 with linux-image-5.3.0-17 after upgraded to the development release Ubuntu Eoan Ermine (development branch). If i boot with linux-image-5.0.0-31-generic the Xorg works well. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21 Uname: Linux 5.0.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Mon Oct 14 11:15:23 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 530 [103c:8054] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 047d:2048 Kensington Orbit Trackball with Scroll Ring Bus 001 Device 002: ID 04d9:a0cd Holtek Semiconductor, Inc. USB Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP EliteDesk 800 G2 SFF ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic root=UUID=714cc192-0d1c-4899-b891-16e6e504c662 ro resume=UUID=316a3e2d-ef98-4c31-8ba1-52e1cd0e8c05 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/19/2019 dmi.bios.vendor: HP dmi.bios.version: N01 Ver. 02.42 dmi.board.name: 8054 dmi.board.vendor: HP dmi.board.version: KBC Version 05.36 dmi.chassis.asset.tag: CZC64082W1 dmi.chassis.type: 4 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrN01Ver.02.42:bd08/19/2019:svnHP:pnHPEliteDesk800G2SFF:pvr:rvnHP:rn8054:rvrKBCVersion05.36:cvnHP:ct4:cvr: dmi.product.family: 103C_53307F G=D dmi.product.name: HP EliteDesk 800 G2 SFF dmi.product.sku: X3J10ET#ABZ dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: eoan DistroRelease: Ubuntu 19.10 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 530 [103c:8054] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 047d:2048 Kensington Orbit Trackball with Scroll Ring Bus 001 Device 002: ID 04d9:a0cd Holtek Semiconductor, Inc. USB Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP EliteDesk 800 G2 SFF Package: xorg-server (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-17-generic root=UUID=714cc192-0d1c-4899-b891-16e6e504c662 ro nomodeset resume=UUID=316a3e2d-ef98-4c31-8ba1-52e1cd0e8c05 ProcVersionSignature: Ubuntu 5.3.0-17.18-generic 5.3.1 Tags: eoan ubuntu Uname: Linux 5.3.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/19/2019 dmi.bios.vendor: HP dmi.bios.version: N01 Ver. 02.42 dmi.board.name: 8054 dmi.board.vendor: HP dmi.board.version: KBC Version 05.36 dmi.chassis.asset.tag: CZC64082W1 dmi.chassis.type: 4 dmi.chassis.vend
[Desktop-packages] [Bug 1846539]
Removing SND_SOC_SOF_BROADWELL_SUPPORT fixes Pixel 2015 audio on Arch default kernel config -- 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/1846539 Title: [broadwell-rt286, playback] Since Linux 5.2rc2 audio playback no longer works on Dell Venue 11 Pro 7140 Status in Linux: Confirmed Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: Hello! I noticed that since Linux 5.2rc2 audio playback no longer works on Dell Venue 11 Pro 7140 (Intel Core M-5Y71; rt286). Turns out that happened because SND_SOC_SOF_BROADWELL_SUPPORT was enabled in kernel binary builds since 5.2rc2: https://kernel.ubuntu.com/~kernel- ppa/mainline/v5.2-rc2/ To verify this assumption I tested two builds of Linux 5.3.1. 1. Build with enabled SND_SOC_SOF_BROADWELL_SUPPORT from https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.3.1/ Audio playback doesn't work, dmesg: [4.072800] snd_hda_intel :00:03.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [4.212606] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.238009] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.294920] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.407351] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.428922] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.458926] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.472113] haswell-pcm-audio haswell-pcm-audio: Direct firmware load for intel/IntcPP01.bin failed with error -2 [4.472118] haswell-pcm-audio haswell-pcm-audio: fw image intel/IntcPP01.bin not available(-2) [4.472735] haswell-pcm-audio haswell-pcm-audio: FW loaded, mailbox readback FW info: type 01, - version: 00.00, build 77, source commit id: 876ac6906f31a43b6772b23c7c983ce9dcb18a19 [4.474607] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> System Pin mapping ok [4.474676] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Offload0 Pin mapping ok [4.474741] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Offload1 Pin mapping ok [4.474807] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Loopback Pin mapping ok [4.476377] broadwell-audio broadwell-audio: rt286-aif1 <-> snd-soc-dummy-dai mapping ok [4.480344] input: broadwell-rt286 Headset as /devices/pci:00/INT3438:00/broadwell-audio/sound/card1/input14 [7.892659] haswell-pcm-audio haswell-pcm-audio: error: message type 7 header 0x8700 [ 13.015379] haswell-pcm-audio haswell-pcm-audio: error: reset stream 2 still running [ 13.127262] haswell-pcm-audio haswell-pcm-audio: error: reset stream 0 still running [ 19.623436] haswell-pcm-audio haswell-pcm-audio: ipc: --message timeout-- ipcx 0x8612 isr 0x ipcd 0x4700 imrx 0x7fff [ 19.623446] haswell-pcm-audio haswell-pcm-audio: ipc: error set dx state 3 faile 2. Build with disabled SND_SOC_SOF_BROADWELL_SUPPORT. Audio playback works, dmesg: [4.839028] haswell-pcm-audio haswell-pcm-audio: Direct firmware load for intel/IntcPP01.bin failed with error -2 [4.839034] haswell-pcm-audio haswell-pcm-audio: fw image intel/IntcPP01.bin not available(-2) [4.839644] haswell-pcm-audio haswell-pcm-audio: FW loaded, mailbox readback FW info: type 01, - version: 00.00, build 77, source commit id: 876ac6906f31a43b6772b23c7c983ce9dcb18a19 [4.851204] snd_hda_intel :00:03.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [4.907386] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> System Pin mapping ok [4.907475] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Offload0 Pin mapping ok [4.909831] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Offload1 Pin mapping ok [4.909931] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Loopback Pin mapping ok [4.912149] broadwell-audio broadwell-audio: rt286-aif1 <-> snd-soc-dummy-dai mapping ok [4.929629] input: broadwell-rt286 Headset as /devices/pci:00/INT3438:00/broadwell-audio/sound/card1/input14 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: irina 818 F pulseaudio /dev/snd/controlC0: irina 818 F pulseaudio CurrentDesktop: GNOME Date: Fri Oct 4 01:22:54 2019 InstallationDate: Installed on 2019-02-12 (233 days ago) InstallationMedia: Ubuntu 18
[Desktop-packages] [Bug 1792085] Re: MTP not working/very slow on Bionic
For those experiencing the slowness problem: I've observed that if you turn on USB Debugging (by enabling Developer Mode) on your android phone, the mtp file transfer then becomes considerably faster. -- 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/1792085 Title: MTP not working/very slow on Bionic Status in libmtp: New Status in gvfs package in Ubuntu: Incomplete Bug description: Hi, unfortunately (for me) MTP android devices no more work on Ubuntu 18.04. I have used MTP on 16.04 without problems, but on 18.04 it does not work. When I connect my Android devices (Samsung A5 and Samsung J3) and I try to list directories with many files (e.g. /DCIM/Camera) the window hangs until I disconnect the device. Same issue if I try to post the command "ls /var/run/1000/gvfs/". I have installed Ubuntu 18.04 on two different machines - an older HP laptop and a recent DELL laptop - and the issue is present on the all of them. I suspect a defect on the "libmtp". I tried many alternative solutions suggested by the net (e.g. jmtpfs and so on) but anyone worked. That's all! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gvfs-fuse 1.36.1-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME Date: Wed Sep 12 06:20:07 2018 LiveMediaBuild: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) 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/libmtp/+bug/1792085/+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 390001] Leo here
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/390001 Title: Gnome visual effects not retained after reboot Status in gnome-control-center package in Ubuntu: Invalid Bug description: Binary package hint: yelp All of the settings specified in the gnome-appearance-properties applet are forgotten when a reboot occurs. This affects all of the windows transitions, mouse cursor sizes and colors, etc. Setting the values to the desired choices appears to take effect in the current session and all changes look fine. However on reboot, all settings return to the (presumable) defaults and none of the prior customization is retained. This occurs on version 9.04 (Jaunty) of UbuntuStudio. System details: System information report, generated by Sysinfo: 6/20/2009 4:03:26 PM http://sourceforge.net/projects/gsysinfo SYSTEM INFORMATION Running Ubuntu Linux, the 5.0 release. GNOME: 2.26.1 (Ubuntu 2009-05-06) Kernel version: 2.6.28-3-rt (#12-Ubuntu SMP PREEMPT RT Fri Apr 17 10:09:11 UTC 2009) GCC: 4.3.3 (i486-linux-gnu) Xorg: unknown (09 April 2009 02:10:02AM) (09 April 2009 02:10:02AM) Hostname: esocid Uptime: 0 days 2 h 20 min CPU INFORMATION GenuineIntel, Intel(R) Pentium(R) 4 CPU 1300MHz Number of CPUs: 1 CPU clock currently at 17000.000 MHz with 256 KB cache Numbering: family(15) model(0) stepping(7) Bogomips: 2594.02 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm up pebs bts MEMORY INFORMATION Total memory: 745 MB Total swap: 2212 MB STORAGE INFORMATION SCSI device - scsi0 Vendor: ATA Model: WDC WD2500JB-00G SCSI device - scsi0 Vendor: ATA Model: ST3160815A SCSI device - scsi1 Vendor: HL-DT-ST Model: DVD-RAM GSA-H55L SCSI device - scsi1 Vendor: HL-DT-ST Model: DVDRAM GSA-4163B HARDWARE INFORMATION MOTHERBOARD Host bridge Intel Corporation 82850 850 (Tehama) Chipset Host Bridge (MCH) (rev 02) PCI bridge(s) Intel Corporation 82850 850 (Tehama) Chipset AGP Bridge (rev 02) Intel Corporation 82801 PCI Bridge (rev 02) Intel Corporation 82850 850 (Tehama) Chipset AGP Bridge (rev 02) Intel Corporation 82801 PCI Bridge (rev 02) USB controller(s) Intel Corporation 82801BA/BAM USB Controller #1 (rev 02) Intel Corporation 82801BA/BAM USB Controller #1 (rev 02) Intel Corporation 82801BA/BAM USB Controller #1 (rev 02) Intel Corporation 82801BA/BAM USB Controller #1 (rev 02) ISA bridge Intel Corporation 82801BA ISA Bridge (LPC) (rev 02) IDE interface Intel Corporation 82801BA IDE U100 Controller (rev 02) (prog-if 80 [Master]) Subsystem: Gateway 2000 Device 0063 GRAPHIC CARD VGA controller ATI Technologies Inc Radeon R100 QD [Radeon 7200] Subsystem: ATI Technologies Inc Device 0538 SOUND CARD Multimedia controller Creative Labs SB Live! EMU10k1 (rev 07) Subsystem: Creative Labs Device 8032 NETWORK Ethernet controller National Semiconductor Corporation DP83815 (MacPhyter) Ethernet Controller Subsystem: Netgear Device f311 ProblemType: Bug Architecture: i386 DistroRelease: Ubuntu 9.04 ExecutablePath: /usr/bin/yelp Package: yelp 2.25.1-0ubuntu5 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: yelp Uname: Linux 2.6.28-3-rt i686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/390001/+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 1850012] [NEW] After log in, sound out/inputs resort to wrong devices
Public bug reported: I really hope I am submitting this bug to the right place, but every time I log in (whether after logout, reboot, etc.) the sound output and input devices resort to my HDMI cable (monitor) and the mic on my webcam instead of the devices I last selected. In previous versions of Ubuntu, if I were to select my speakers as the output device, they would remain the default until I changed it again, even after logout/log in. Now, whenever I log in, the sound still comes out of my speakers, but adjusting the volume does not work properly until I go into settings > sound > and then reselect my speakers as the output device. The volume indicator pops up on screen and it shows the sound going up or down, but it says it is adjusting the sound to my HDMI cable instead and it has no effect on my desktop speakers. I really hope that makes sense. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 26 21:20:59 2019 InstallationDate: Installed on 2018-12-22 (308 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all ProcEnviron: 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:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: SPDIF Out, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [System Product Name, Realtek ALC887-VD, SPDIF Out, Internal] Playback problem UpgradeStatus: Upgraded to eoan on 2019-10-14 (12 days ago) dmi.bios.date: 09/06/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0410 dmi.board.asset.tag: Default string dmi.board.name: Z170M-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0410:bd09/06/2015:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170M-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- 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/1850012 Title: After log in, sound out/inputs resort to wrong devices Status in alsa-driver package in Ubuntu: New Bug description: I really hope I am submitting this bug to the right place, but every time I log in (whether after logout, reboot, etc.) the sound output and input devices resort to my HDMI cable (monitor) and the mic on my webcam instead of the devices I last selected. In previous versions of Ubuntu, if I were to select my speakers as the output device, they would remain the default until I changed it again, even after logout/log in. Now, whenever I log in, the sound still comes out of my speakers, but adjusting the volume does not work properly until I go into settings > sound > and then reselect my speakers as the output device. The volume indicator pops up on screen and it shows the sound going up or down, but it says it is adjusting the sound to my HDMI cable instead and it has no effect on my desktop speakers. I really hope that makes sense. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 26 21:20:59 2019 InstallationDate: Installed on 2018-12-22 (308 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all ProcEnviron: 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:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: SPDIF Out, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [System Product Name, Realtek ALC887-VD, SPDIF Out, Internal] Playback problem UpgradeStatus: Upgraded to eoan on 2019-10-14 (12 days ago) dmi.bios.date: 09/06/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0410
[Desktop-packages] [Bug 1850010] [NEW] package xserver-xorg-video-nvidia-430 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/nvidia/xorg/nvidia_drv.so', which
Public bug reported: Nvidia laptop support is basically nonexistent for linux. I've had nothing but problems with Ubuntu ProblemType: Package DistroRelease: Ubuntu 19.10 Package: xserver-xorg-video-nvidia-430 (not installed) ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 Date: Sat Oct 26 18:56:24 2019 DpkgTerminalLog: Preparing to unpack .../xserver-xorg-video-nvidia-430_430.50-0ubuntu2_amd64.deb ... Unpacking xserver-xorg-video-nvidia-430 (430.50-0ubuntu2) ... [1mdpkg:[0m error processing archive /var/cache/apt/archives/xserver-xorg-video-nvidia-430_430.50-0ubuntu2_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/nvidia/xorg/nvidia_drv.so', which is also in package xserver-xorg-video-nvidia-440 440.26-0ubuntu0~gpu19.10.2 ErrorMessage: trying to overwrite '/usr/lib/x86_64-linux-gnu/nvidia/xorg/nvidia_drv.so', which is also in package xserver-xorg-video-nvidia-440 440.26-0ubuntu0~gpu19.10.2 InstallationDate: Installed on 2019-10-26 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Python3Details: /usr/bin/python3.7, Python 3.7.5rc1, python3-minimal, 3.7.5-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: nvidia-graphics-drivers-430 Title: package xserver-xorg-video-nvidia-430 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/nvidia/xorg/nvidia_drv.so', which is also in package xserver-xorg-video-nvidia-440 440.26-0ubuntu0~gpu19.10.2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-430 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package eoan -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-430 in Ubuntu. https://bugs.launchpad.net/bugs/1850010 Title: package xserver-xorg-video-nvidia-430 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux- gnu/nvidia/xorg/nvidia_drv.so', which is also in package xserver-xorg- video-nvidia-440 440.26-0ubuntu0~gpu19.10.2 Status in nvidia-graphics-drivers-430 package in Ubuntu: New Bug description: Nvidia laptop support is basically nonexistent for linux. I've had nothing but problems with Ubuntu ProblemType: Package DistroRelease: Ubuntu 19.10 Package: xserver-xorg-video-nvidia-430 (not installed) ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 Date: Sat Oct 26 18:56:24 2019 DpkgTerminalLog: Preparing to unpack .../xserver-xorg-video-nvidia-430_430.50-0ubuntu2_amd64.deb ... Unpacking xserver-xorg-video-nvidia-430 (430.50-0ubuntu2) ... [1mdpkg:[0m error processing archive /var/cache/apt/archives/xserver-xorg-video-nvidia-430_430.50-0ubuntu2_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/nvidia/xorg/nvidia_drv.so', which is also in package xserver-xorg-video-nvidia-440 440.26-0ubuntu0~gpu19.10.2 ErrorMessage: trying to overwrite '/usr/lib/x86_64-linux-gnu/nvidia/xorg/nvidia_drv.so', which is also in package xserver-xorg-video-nvidia-440 440.26-0ubuntu0~gpu19.10.2 InstallationDate: Installed on 2019-10-26 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Python3Details: /usr/bin/python3.7, Python 3.7.5rc1, python3-minimal, 3.7.5-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: nvidia-graphics-drivers-430 Title: package xserver-xorg-video-nvidia-430 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/nvidia/xorg/nvidia_drv.so', which is also in package xserver-xorg-video-nvidia-440 440.26-0ubuntu0~gpu19.10.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-430/+bug/1850010/+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 1850009] [NEW] Issue with detecting new state in dhclient-enter-hooks.d/resolved
Public bug reported: After upgrading to 19.10 I noticed that resolving hostnames stopped working. Quick release, which package and version info: root@caret:~# lsb_release -r Release:19.10 root@caret:~# dpkg -S /etc/dhcp/dhclient-enter-hooks.d/resolved systemd: /etc/dhcp/dhclient-enter-hooks.d/resolved root@caret:~# apt-cache policy systemd systemd: Installed: 242-7ubuntu3 Candidate: 242-7ubuntu3 Version table: *** 242-7ubuntu3 500 500 http://au.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status The file /etc/resolv.conf was pointing to the local instance of systemd-resolved however there was no search line, indicating something wasn't quite right. Restarting the systemd-resolved service did recreate /etc/resolv.conf with expected search line. After much debugging, I've worked out what was going wrong. The dhcp hook file /etc/dhcp/dhclient-enter-hooks.d/resolved has a bug in the resolver state change logic. This may also impact on tickets 1805183, 1832050, 1832053 and maybe others. When doing the md5sum of the old and new state, the command is wrong. It isn't sending STDOUT (and optionally STDERR) to the temp file but rather putting the md5sum command into the background and then creating an empty file for both states. Which obviously isn't different, so systemd- resolved doesn't restart. Quick diff of a working version (I'm not capturing STDERR but one can with "2>&1") === BEGIN PATCH === *** .brk-resolved-20191027 2019-10-27 11:19:56.210069032 +1030 --- resolved2019-10-27 11:30:17.156381734 +1030 *** *** 30,36 mkdir -p $statedir oldstate="$(mktemp)" ! md5sum $statedir/isc-dhcp-v4-$interface.conf $statedir/isc-dhcp-v6-$interface.conf &> $oldstate if [ -n "$new_domain_name_servers" ] ; then cat <$statedir/isc-dhcp-v4-$interface.conf [Resolve] --- 30,36 mkdir -p $statedir oldstate="$(mktemp)" ! md5sum $statedir/isc-dhcp-v4-$interface.conf $statedir/isc-dhcp-v6-$interface.conf > $oldstate if [ -n "$new_domain_name_servers" ] ; then cat <$statedir/isc-dhcp-v4-$interface.conf [Resolve] *** *** 55,61 fi newstate="$(mktemp)" ! md5sum $statedir/isc-dhcp-v4-$interface.conf $statedir/isc-dhcp-v6-$interface.conf &> $newstate if ! cmp $oldstate $newstate; then systemctl try-reload-or-restart systemd-resolved.service fi --- 55,61 fi newstate="$(mktemp)" ! md5sum $statedir/isc-dhcp-v4-$interface.conf $statedir/isc-dhcp-v6-$interface.conf > $newstate if ! cmp $oldstate $newstate; then systemctl try-reload-or-restart systemd-resolved.service fi === END PATCH === Also, the script removes the script removes the $oldstate file but doesn't remove the $newstate file. Not sure how this made it through QA testing... But breaking DHCP client shouldn't happen like this. ivan. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: network-manager 1.20.4-2ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 Date: Sun Oct 27 11:48:33 2019 InstallationDate: Installed on 2017-04-21 (918 days ago) InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 (20170412) IpRoute: default via 172.16.1.14 dev enp0s5 150.101.89.32/28 dev enp0s5 scope link 169.254.0.0/16 dev enp0s5 scope link metric 1000 172.16.1.0/24 dev enp0s5 proto kernel scope link src 172.16.1.120 IwConfig: lono wireless extensions. enp0s5no wireless extensions. NetworkManager.state: [main] NetworkingEnabled=false WirelessEnabled=true WWANEnabled=true ProcEnviron: LANGUAGE=en_AU:en TERM=vt100 PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash RfKill: SourcePackage: network-manager UpgradeStatus: Upgraded to eoan on 2019-10-26 (0 days ago) nmcli-con: nmcli-dev: DEVICE TYPE STATE IP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH enp0s5 ethernet unmanaged unknown unknown /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged unknown unknown /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.20.4 connected started unknown disabledenabled enabled enabled enabled ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ** Package changed: network-man
[Desktop-packages] [Bug 1724876] Re: libreoffice soffice.bin using 100% cpu
Also, here was my work-around to try to fix the 100% cpu soffice.bin bug: https://serverfault.com/questions/953809/soffice-bin-high-cpu- usage/986039#986039. -- 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/1724876 Title: libreoffice soffice.bin using 100% cpu Status in libreoffice package in Ubuntu: Incomplete Bug description: With literally every action in libreoffice Calc, CPU usage goes to 100% due to soffice.bin, and stays on 100% for minutes. To the extend that libreoffice calc is UNUSABLE for anything that has to do with spreadsheets. As far as I am concerned, this is a critical bug because it makes the program unusable, and often even the complete computer due to the high cpu load. - 'Every action' includes typing as much as one single letter in a cell. Or opening the file. - the file I am working on is only 1.1Mb in size - the same file used to open fine in previous versions of libreoffice. what I've tried so far - without any improvement in speed: - under tools, options, assigned memory 256 Mb for Libreoffice, and 20Mb per object (no solution) - automatic calculation has been turned off (no solution) - libreoffice-gnome and libreoffice-gtk have been removed (no solution) - purged and reinstalled libreoffice. (no solution) - created new user profile - also no resolve System: Ubuntu 16.04 LTS on AMD A8 with 8Gb ram and running on an SSD. Libreoffice: Version: 5.1.6.2 Build ID: 1:5.1.6~rc2-0ubuntu1~xenial2 CPU Threads: 4; OS Version: Linux 4.4; UI Render: default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1724876/+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 1724876] Re: libreoffice soffice.bin using 100% cpu
Marcus, here's all the extensions I have installed. Also, I just downgraded my LibreOffice installation from 6.3.2 to 6.3.1 then to 6.2.8. 6.3.2 and 6.3.1 both were buggy, but 6.2.8 seems to work perfectly now and actually makes my entire computer feel like I just bought a new computer! All of a sudden it feels totally usable again! Here's my bug report I just made on this. It may be related: https://bugs.documentfoundation.org/show_bug.cgi?id=128406. See also this (appears to be the *exact* same problem as my bug report above): https://ask.libreoffice.org/en/question/208712/calc-6312-macro- button-problem/ ** Bug watch added: Document Foundation Bugzilla #128406 https://bugs.documentfoundation.org/show_bug.cgi?id=128406 ** Attachment added: "Selection_021.png" https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1724876/+attachment/5300482/+files/Selection_021.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/1724876 Title: libreoffice soffice.bin using 100% cpu Status in libreoffice package in Ubuntu: Incomplete Bug description: With literally every action in libreoffice Calc, CPU usage goes to 100% due to soffice.bin, and stays on 100% for minutes. To the extend that libreoffice calc is UNUSABLE for anything that has to do with spreadsheets. As far as I am concerned, this is a critical bug because it makes the program unusable, and often even the complete computer due to the high cpu load. - 'Every action' includes typing as much as one single letter in a cell. Or opening the file. - the file I am working on is only 1.1Mb in size - the same file used to open fine in previous versions of libreoffice. what I've tried so far - without any improvement in speed: - under tools, options, assigned memory 256 Mb for Libreoffice, and 20Mb per object (no solution) - automatic calculation has been turned off (no solution) - libreoffice-gnome and libreoffice-gtk have been removed (no solution) - purged and reinstalled libreoffice. (no solution) - created new user profile - also no resolve System: Ubuntu 16.04 LTS on AMD A8 with 8Gb ram and running on an SSD. Libreoffice: Version: 5.1.6.2 Build ID: 1:5.1.6~rc2-0ubuntu1~xenial2 CPU Threads: 4; OS Version: Linux 4.4; UI Render: default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1724876/+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 1841953] Re: Bionic ⋅ SuperTuxKart ⋅ Flickering shadows ⋅ Haswell i915
As I feared from trying with Ubuntu 19.10, using ppa:ubuntu-x-swat/updates on 18.04 did not fix the flickering-shadows problem. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1841953 Title: Bionic ⋅ SuperTuxKart ⋅ Flickering shadows ⋅ Haswell i915 Status in mesa package in Ubuntu: Incomplete Status in supertuxkart package in Ubuntu: New Bug description: Hi, for few weeks now, I've noticed a big change in graphic performance while playing famous SuperTuxKart on ubuntu bionic : shadows are flickering, all over the screen, it's a big pain for eyes ( and wonder what would happen for epileptic people ). My computer is : Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz with 16Go ram and Haswell integrated graphics. coeur-noir@asgard:~$ lspci -k | grep -A 2 -i "VGA" 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller (rev 06) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller Kernel driver in use: i915 coeur-noir@asgard:~$ sudo lshw -c video *-display description: VGA compatible controller produit: Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller fabriquant: Intel Corporation identifiant matériel: 2 information bus: pci@:00:02.0 version: 06 bits: 64 bits horloge: 33MHz fonctionnalités: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 ressources: irq:26 mémoire:f780-f7bf mémoire:e000-efff portE/S:f000(taille=64) mémoire:c-d coeur-noir@asgard:~$ My Ubuntu Budgie 18.04 is : coeur-noir@asgard:~$ lsb_release -rd Description: Ubuntu 18.04.3 LTS Release: 18.04 coeur-noir@asgard:~$ uname -a Linux asgard 5.0.0-23-generic #24~18.04.1-Ubuntu SMP Mon Jul 29 16:12:28 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux coeur-noir@asgard:~$ mesa packages are : coeur-noir@asgard:~$ dpkg -l | grep mesa ii libegl-mesa0:amd64 19.0.8-0ubuntu0~18.04.1 amd64free implementation of the EGL API -- Mesa vendor library ii libegl1-mesa:amd64 19.0.8-0ubuntu0~18.04.1 amd64transitional dummy package ii libgl1-mesa-dri:amd64 19.0.8-0ubuntu0~18.04.1 amd64free implementation of the OpenGL API -- DRI modules ii libgl1-mesa-dri:i38619.0.8-0ubuntu0~18.04.1 i386 free implementation of the OpenGL API -- DRI modules ii libgl1-mesa-glx:amd64 19.0.8-0ubuntu0~18.04.1 amd64transitional dummy package ii libgl1-mesa-glx:i38619.0.8-0ubuntu0~18.04.1 i386 transitional dummy package ii libglapi-mesa:amd64 19.0.8-0ubuntu0~18.04.1 amd64free implementation of the GL API -- shared library ii libglapi-mesa:i386 19.0.8-0ubuntu0~18.04.1 i386 free implementation of the GL API -- shared library ii libgles2-mesa:amd64 19.0.8-0ubuntu0~18.04.1 amd64transitional dummy package ii libglu1-mesa:amd64 9.0.0-2.1build1 amd64Mesa OpenGL utility library (GLU) ii libglu1-mesa:i386 9.0.0-2.1build1 i386 Mesa OpenGL utility library (GLU) ii libglx-mesa0:amd64 19.0.8-0ubuntu0~18.04.1 amd64free implementation of the OpenGL API -- GLX vendor library ii libglx-mesa0:i386 19.0.8-0ubuntu0~18.04.1 i386 free implementation of the OpenGL API -- GLX vendor library ii libosmesa6:amd6419.0.8-0ubuntu0~18.04.1 amd64Mesa Off-screen rendering extension ii libosmesa6:i386 19.0.8-0ubuntu0~18.04.1 i386 Mesa Off-screen rendering extension ii libwayland-egl1-mesa:amd64 19.0.8-0ubuntu0~18.04.1 amd64transitional dummy package ii mesa-utils 8.4.0-1 amd64Miscellaneous Mesa GL utilities ii mesa-utils-extra8.4.0-1 amd64Miscellaneous Mesa utilies (opengles, egl) ii mesa-va-drivers:amd64 19.0.8-0ubuntu0~18.04.1 amd64Mesa VA-API video acceleration driver
[Desktop-packages] [Bug 1850001] [NEW] nautilus hangs on file delete
Public bug reported: Nautilus hangs when deleting a file. The file does not get deleted. This applies to the DELETE key, the SHIFT+DELETE keys, and the RIGHT- CLICK attempt at deleting. This is reproducible in this boot session. This has never happened since the install of the OS. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: nautilus 1:3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 26 18:12:36 2019 ExecutablePath: /usr/bin/nautilus GsettingsChanges: InstallationDate: Installed on 2019-10-20 (6 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191014) ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- 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/1850001 Title: nautilus hangs on file delete Status in nautilus package in Ubuntu: New Bug description: Nautilus hangs when deleting a file. The file does not get deleted. This applies to the DELETE key, the SHIFT+DELETE keys, and the RIGHT- CLICK attempt at deleting. This is reproducible in this boot session. This has never happened since the install of the OS. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: nautilus 1:3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 26 18:12:36 2019 ExecutablePath: /usr/bin/nautilus GsettingsChanges: InstallationDate: Installed on 2019-10-20 (6 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191014) ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1850001/+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 1841953] Re: Bionic ⋅ SuperTuxKart ⋅ Flickering shadows ⋅ Haswell i915
I'll try that and report, thanks. Meanwhile I have tried with Ubuntu ( default ) 19.10 and same problem… -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1841953 Title: Bionic ⋅ SuperTuxKart ⋅ Flickering shadows ⋅ Haswell i915 Status in mesa package in Ubuntu: Incomplete Status in supertuxkart package in Ubuntu: New Bug description: Hi, for few weeks now, I've noticed a big change in graphic performance while playing famous SuperTuxKart on ubuntu bionic : shadows are flickering, all over the screen, it's a big pain for eyes ( and wonder what would happen for epileptic people ). My computer is : Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz with 16Go ram and Haswell integrated graphics. coeur-noir@asgard:~$ lspci -k | grep -A 2 -i "VGA" 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller (rev 06) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller Kernel driver in use: i915 coeur-noir@asgard:~$ sudo lshw -c video *-display description: VGA compatible controller produit: Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller fabriquant: Intel Corporation identifiant matériel: 2 information bus: pci@:00:02.0 version: 06 bits: 64 bits horloge: 33MHz fonctionnalités: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 ressources: irq:26 mémoire:f780-f7bf mémoire:e000-efff portE/S:f000(taille=64) mémoire:c-d coeur-noir@asgard:~$ My Ubuntu Budgie 18.04 is : coeur-noir@asgard:~$ lsb_release -rd Description: Ubuntu 18.04.3 LTS Release: 18.04 coeur-noir@asgard:~$ uname -a Linux asgard 5.0.0-23-generic #24~18.04.1-Ubuntu SMP Mon Jul 29 16:12:28 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux coeur-noir@asgard:~$ mesa packages are : coeur-noir@asgard:~$ dpkg -l | grep mesa ii libegl-mesa0:amd64 19.0.8-0ubuntu0~18.04.1 amd64free implementation of the EGL API -- Mesa vendor library ii libegl1-mesa:amd64 19.0.8-0ubuntu0~18.04.1 amd64transitional dummy package ii libgl1-mesa-dri:amd64 19.0.8-0ubuntu0~18.04.1 amd64free implementation of the OpenGL API -- DRI modules ii libgl1-mesa-dri:i38619.0.8-0ubuntu0~18.04.1 i386 free implementation of the OpenGL API -- DRI modules ii libgl1-mesa-glx:amd64 19.0.8-0ubuntu0~18.04.1 amd64transitional dummy package ii libgl1-mesa-glx:i38619.0.8-0ubuntu0~18.04.1 i386 transitional dummy package ii libglapi-mesa:amd64 19.0.8-0ubuntu0~18.04.1 amd64free implementation of the GL API -- shared library ii libglapi-mesa:i386 19.0.8-0ubuntu0~18.04.1 i386 free implementation of the GL API -- shared library ii libgles2-mesa:amd64 19.0.8-0ubuntu0~18.04.1 amd64transitional dummy package ii libglu1-mesa:amd64 9.0.0-2.1build1 amd64Mesa OpenGL utility library (GLU) ii libglu1-mesa:i386 9.0.0-2.1build1 i386 Mesa OpenGL utility library (GLU) ii libglx-mesa0:amd64 19.0.8-0ubuntu0~18.04.1 amd64free implementation of the OpenGL API -- GLX vendor library ii libglx-mesa0:i386 19.0.8-0ubuntu0~18.04.1 i386 free implementation of the OpenGL API -- GLX vendor library ii libosmesa6:amd6419.0.8-0ubuntu0~18.04.1 amd64Mesa Off-screen rendering extension ii libosmesa6:i386 19.0.8-0ubuntu0~18.04.1 i386 Mesa Off-screen rendering extension ii libwayland-egl1-mesa:amd64 19.0.8-0ubuntu0~18.04.1 amd64transitional dummy package ii mesa-utils 8.4.0-1 amd64Miscellaneous Mesa GL utilities ii mesa-utils-extra8.4.0-1 amd64Miscellaneous Mesa utilies (opengles, egl) ii mesa-va-drivers:amd64 19.0.8-0ubuntu0~18.04.1 amd64Mesa VA-API video acceleration drivers ii mesa-vdpau-dri
[Desktop-packages] [Bug 1849930] Re: Additional VPN Breaks First VPN
This doesn't fix the underlying bug, but I was able to find a workaround that repairs the corruption caused by the bug. See here: https://askubuntu.com/a/1184070/256054 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1849930 Title: Additional VPN Breaks First VPN Status in gnome-control-center: New Status in NetworkManager: New Status in strongSwan: New Status in gnome-control-center package in Ubuntu: New Bug description: When I add only one L2TP VPN profile to gnome-control-center's Network > VPN settings, it works fine. However, if I add a 2nd L2TP VPN, the 2nd L2TP VPN, not only doesn't work, but it corrupts the first L2TP VPN so that it too stops working. Furthermore, if I remove 2nd L2TP VPN profile (that corrupted the first L2TP VPN) this does NOT repair the corruption to the first L2TP VPN, it remains corrupted. Additionally, removing all VPN profiles and re-adding the first one back, doesn't repair the corruption. Rebooting and adding them back doesn't work either. The only thing that works, that I've found, is completely reinstalling Ubuntu 19.10. Please advise better workarounds than reinstalling. In case it matters, these additional packages were also required for my initial VPN setup: sudo apt-get install -y network-manager-l2tp network-manager-l2tp- gnome strongswan Here's what's in the syslog on a failed VPN Connection attempt: Oct 26 02:58:35 workstation5 NetworkManager[1241]: [1572076715.5632] audit: op="connection-activate" uuid="1942cf95-93b1-4e74-a44a-947a46bffb5a" name="L2TP VPN1" pid=3531 uid=1000 result="success" Oct 26 02:58:35 workstation5 NetworkManager[1241]: [1572076715.5702] vpn-connection[0x5642f421c750,1932cf95-91b1-4e85-a44a-498a56befb5a,"L2TP VPN1",0]: Started the VPN service, PID 7273 Oct 26 02:58:35 workstation5 NetworkManager[1241]: [1572076715.5747] vpn-connection[0x5642f421c750,1932cf95-91b1-4e85-a44a-498a56befb5a,"L2TP VPN1",0]: Saw the service appear; activating connection Oct 26 02:58:35 workstation5 NetworkManager[1241]: [1572076715.6566] vpn-connection[0x5642f421c750,1932cf95-91b1-4e85-a44a-498a56befb5a,"L2TP VPN1",0]: VPN connection: (ConnectInteractive) reply received Oct 26 02:58:35 workstation5 NetworkManager[1241]: Stopping strongSwan IPsec failed: starter is not running Oct 26 02:58:37 workstation5 NetworkManager[1241]: Starting strongSwan 5.7.2 IPsec [starter]... Oct 26 02:58:37 workstation5 NetworkManager[1241]: Loading config setup Oct 26 02:58:37 workstation5 NetworkManager[1241]: Loading conn '1942cf95-93b1-4e74-a44a-947a46bffb5a' Oct 26 02:58:37 workstation5 NetworkManager[1241]: found netkey IPsec stack Oct 26 02:58:48 workstation5 NetworkManager[1241]: Stopping strongSwan IPsec... Oct 26 02:58:48 workstation5 NetworkManager[1241]: initiating Main Mode IKE_SA 1942cf95-93b1-4e74-a44a-947a46bffb5a[1] to 49.230.24.121 Oct 26 02:58:48 workstation5 NetworkManager[1241]: generating ID_PROT request 0 [ SA V V V V V ] Oct 26 02:58:48 workstation5 NetworkManager[1241]: sending packet: from 192.168.1.2[500] to 49.230.24.121[500] (236 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: received packet: from 49.230.24.121[500] to 192.168.1.2[500] (156 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: parsed ID_PROT response 0 [ SA V V V V ] Oct 26 02:58:48 workstation5 NetworkManager[1241]: received XAuth vendor ID Oct 26 02:58:48 workstation5 NetworkManager[1241]: received DPD vendor ID Oct 26 02:58:48 workstation5 NetworkManager[1241]: received FRAGMENTATION vendor ID Oct 26 02:58:48 workstation5 NetworkManager[1241]: received NAT-T (RFC 3947) vendor ID Oct 26 02:58:48 workstation5 NetworkManager[1241]: selected proposal: IKE:3DES_CBC/HMAC_SHA1_96/PRF_HMAC_SHA1/MODP_1024 Oct 26 02:58:48 workstation5 NetworkManager[1241]: generating ID_PROT request 0 [ KE No NAT-D NAT-D ] Oct 26 02:58:48 workstation5 NetworkManager[1241]: sending packet: from 192.168.1.2[500] to 49.230.24.121[500] (244 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: received packet: from 49.230.24.121[500] to 192.168.1.2[500] (244 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: parsed ID_PROT response 0 [ KE No NAT-D NAT-D ] Oct 26 02:58:48 workstation5 NetworkManager[1241]: local host is behind NAT, sending keep alives Oct 26 02:58:48 workstation5 NetworkManager[1241]: generating ID_PROT request 0 [ ID HASH ] Oct 26 02:58:48 workstation5 NetworkManager[1241]: sending packet: from 192.168.1.2[4500] to 49.230.24.121[4500] (68 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: received packet: from 49.230.24.121[500] to 192.168.1.2[500] (68 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: invalid HASH_V1 payload length, decryption failed? Oct 26 02:58:48 workstation5 NetworkM
[Desktop-packages] [Bug 1849996] Re: package lirc 0.10.1-6 failed to install/upgrade: installed lirc package post-installati│···········································································
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lirc in Ubuntu. https://bugs.launchpad.net/bugs/1849996 Title: package lirc 0.10.1-6 failed to install/upgrade: installed lirc package post- installati│·· Status in lirc package in Ubuntu: New Bug description: Standard do-release-upgrade ProblemType: Package DistroRelease: Ubuntu 19.10 Package: lirc 0.10.1-6 ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 Date: Sat Oct 26 15:12:22 2019 ErrorMessage: installed lirc package post-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.7, Python 3.7.5rc1, python3-minimal, 3.7.5-1 PythonDetails: /usr/bin/python2.7, Python 2.7.17rc1, python-minimal, 2.7.17-1 RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: lirc Title: package lirc 0.10.1-6 failed to install/upgrade: installed lirc package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to eoan on 2019-10-26 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/1849996/+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] Re: Full-tunnel VPN DNS leakage regression
The netplan.io (arm64) autopkgtest failure (due to timeout) has been retried today, it passed: http://autopkgtest.ubuntu.com/packages/n/netplan.io/bionic/arm64 No more failure reported in pending sru page. - Eric -- 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: Confirmed Status in network-manager package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in network-manager source package in Xenial: Confirmed Status in systemd source package in Xenial: Invalid Status in network-manager source package in Bionic: Fix Committed Status in systemd source package in Bionic: Fix Released Status in network-manager source package in Cosmic: Fix Released Status in systemd source package in Cosmic: Fix Released 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 1849996] [NEW] package lirc 0.10.1-6 failed to install/upgrade: installed lirc package post-installati│·········································································
Public bug reported: Standard do-release-upgrade ProblemType: Package DistroRelease: Ubuntu 19.10 Package: lirc 0.10.1-6 ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 Date: Sat Oct 26 15:12:22 2019 ErrorMessage: installed lirc package post-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.7, Python 3.7.5rc1, python3-minimal, 3.7.5-1 PythonDetails: /usr/bin/python2.7, Python 2.7.17rc1, python-minimal, 2.7.17-1 RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: lirc Title: package lirc 0.10.1-6 failed to install/upgrade: installed lirc package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to eoan on 2019-10-26 (0 days ago) ** Affects: lirc (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package eoan -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lirc in Ubuntu. https://bugs.launchpad.net/bugs/1849996 Title: package lirc 0.10.1-6 failed to install/upgrade: installed lirc package post- installati│·· Status in lirc package in Ubuntu: New Bug description: Standard do-release-upgrade ProblemType: Package DistroRelease: Ubuntu 19.10 Package: lirc 0.10.1-6 ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 Date: Sat Oct 26 15:12:22 2019 ErrorMessage: installed lirc package post-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.7, Python 3.7.5rc1, python3-minimal, 3.7.5-1 PythonDetails: /usr/bin/python2.7, Python 2.7.17rc1, python-minimal, 2.7.17-1 RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: lirc Title: package lirc 0.10.1-6 failed to install/upgrade: installed lirc package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to eoan on 2019-10-26 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/1849996/+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 1848852] Re: Counter-Strike Global Offensive freezes in gnome-shell
I hope someone can fix this, is very annoying. -- 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/1848852 Title: Counter-Strike Global Offensive freezes in gnome-shell Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Triaged Bug description: After upgrade to ubuntu 19.10, when I launch counter strike global offensive from steam the game is frozen. I can alt-tab and close the game. Tried in fluxbox window manager where the game works, changed fullscreen to windowed fullscreen in the options and tried on gnome again, now the desktop isn't responding after launching the game and I had to ctrl-alt-f3 to reboot my machine. Using a Radeon RX 580 video card. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1848852/+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 1849930] Re: Additional VPN Breaks First VPN
** Description changed: When I add only one L2TP VPN profile to gnome-control-center's Network > VPN settings, it works fine. However, if I add a 2nd L2TP VPN, the 2nd L2TP VPN, not only doesn't work, but it corrupts the first L2TP VPN so that it too stops working. Furthermore, if I remove 2nd L2TP VPN profile (that corrupted the first L2TP VPN) this does NOT repair the corruption to the first L2TP VPN, it remains corrupted. Additionally, removing all VPN profiles and re-adding the first one back, doesn't repair the corruption. Rebooting and adding them back doesn't work either. The only thing that works, that I've found, is completely reinstalling Ubuntu 19.10. Please advise better workarounds than reinstalling. + + In case it matters, these additional packages were also required for my + initial VPN setup: + + sudo apt-get install -y network-manager-l2tp network-manager-l2tp-gnome + strongswan Here's what's in the syslog on a failed VPN Connection attempt: Oct 26 02:58:35 workstation5 NetworkManager[1241]: [1572076715.5632] audit: op="connection-activate" uuid="1942cf95-93b1-4e74-a44a-947a46bffb5a" name="L2TP VPN1" pid=3531 uid=1000 result="success" Oct 26 02:58:35 workstation5 NetworkManager[1241]: [1572076715.5702] vpn-connection[0x5642f421c750,1932cf95-91b1-4e85-a44a-498a56befb5a,"L2TP VPN1",0]: Started the VPN service, PID 7273 Oct 26 02:58:35 workstation5 NetworkManager[1241]: [1572076715.5747] vpn-connection[0x5642f421c750,1932cf95-91b1-4e85-a44a-498a56befb5a,"L2TP VPN1",0]: Saw the service appear; activating connection Oct 26 02:58:35 workstation5 NetworkManager[1241]: [1572076715.6566] vpn-connection[0x5642f421c750,1932cf95-91b1-4e85-a44a-498a56befb5a,"L2TP VPN1",0]: VPN connection: (ConnectInteractive) reply received Oct 26 02:58:35 workstation5 NetworkManager[1241]: Stopping strongSwan IPsec failed: starter is not running Oct 26 02:58:37 workstation5 NetworkManager[1241]: Starting strongSwan 5.7.2 IPsec [starter]... Oct 26 02:58:37 workstation5 NetworkManager[1241]: Loading config setup Oct 26 02:58:37 workstation5 NetworkManager[1241]: Loading conn '1942cf95-93b1-4e74-a44a-947a46bffb5a' Oct 26 02:58:37 workstation5 NetworkManager[1241]: found netkey IPsec stack Oct 26 02:58:48 workstation5 NetworkManager[1241]: Stopping strongSwan IPsec... Oct 26 02:58:48 workstation5 NetworkManager[1241]: initiating Main Mode IKE_SA 1942cf95-93b1-4e74-a44a-947a46bffb5a[1] to 49.230.24.121 Oct 26 02:58:48 workstation5 NetworkManager[1241]: generating ID_PROT request 0 [ SA V V V V V ] Oct 26 02:58:48 workstation5 NetworkManager[1241]: sending packet: from 192.168.1.2[500] to 49.230.24.121[500] (236 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: received packet: from 49.230.24.121[500] to 192.168.1.2[500] (156 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: parsed ID_PROT response 0 [ SA V V V V ] Oct 26 02:58:48 workstation5 NetworkManager[1241]: received XAuth vendor ID Oct 26 02:58:48 workstation5 NetworkManager[1241]: received DPD vendor ID Oct 26 02:58:48 workstation5 NetworkManager[1241]: received FRAGMENTATION vendor ID Oct 26 02:58:48 workstation5 NetworkManager[1241]: received NAT-T (RFC 3947) vendor ID Oct 26 02:58:48 workstation5 NetworkManager[1241]: selected proposal: IKE:3DES_CBC/HMAC_SHA1_96/PRF_HMAC_SHA1/MODP_1024 Oct 26 02:58:48 workstation5 NetworkManager[1241]: generating ID_PROT request 0 [ KE No NAT-D NAT-D ] Oct 26 02:58:48 workstation5 NetworkManager[1241]: sending packet: from 192.168.1.2[500] to 49.230.24.121[500] (244 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: received packet: from 49.230.24.121[500] to 192.168.1.2[500] (244 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: parsed ID_PROT response 0 [ KE No NAT-D NAT-D ] Oct 26 02:58:48 workstation5 NetworkManager[1241]: local host is behind NAT, sending keep alives Oct 26 02:58:48 workstation5 NetworkManager[1241]: generating ID_PROT request 0 [ ID HASH ] Oct 26 02:58:48 workstation5 NetworkManager[1241]: sending packet: from 192.168.1.2[4500] to 49.230.24.121[4500] (68 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: received packet: from 49.230.24.121[500] to 192.168.1.2[500] (68 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: invalid HASH_V1 payload length, decryption failed? Oct 26 02:58:48 workstation5 NetworkManager[1241]: could not decrypt payloads Oct 26 02:58:48 workstation5 NetworkManager[1241]: message parsing failed Oct 26 02:58:48 workstation5 NetworkManager[1241]: ignore malformed INFORMATIONAL request Oct 26 02:58:48 workstation5 NetworkManager[1241]: INFORMATIONAL_V1 request with message ID 3016741680 processing failed Oct 26 02:58:48 workstation5 NetworkManager[1241]: sending retransmit 1 of request message ID 0, seq 3 Oct 26 02:58:48 workstation5 NetworkManager[1241]: sending packet: from 192.168.1.2
[Desktop-packages] [Bug 1849987] [NEW] empty space when on list view and when back to icon view
Public bug reported: Description: Ubuntu 19.10 Release: 19.10 nautilus: Installed: 1:3.34.1-1ubuntu1 Candidate: 1:3.34.1-1ubuntu1 Expected behavior: - (1) Open nautilus in list view OR (2) Open Nautilus in icon view and then switch to list view - List view occupies all the space between the top bar and the bottom. - Switch to icon view - Icon view occupies all the space between the top bar and the bottom. Actual Behavior - (1) Open nautilus in list view OR (2) Open Nautilus in icon view and then switch to list view - List view occupies approximately 55% of the space between the top bar and the bottom. Approximately 45% of the space between the top bar and the bottom is blank (the upmost part). - Switch to icon view - Icon view occupies approximately 55% of the space between the top bar and the bottom. Approximately 45% of the space between the top bar and the bottom is blank (the upmost part). Observations: - The side bar doesn't seem to affect the bug. - By Starting nautilus in icon view the bug doesn't occur. In this case it's only triggered when switching to list view. - There are only 2 known ways to revert the bug: (1) when on icon view, clicking on "Other Locations", and then back to any section. (2) by restarting nautilus. There is no known way to revert the bug in list view. I am on Ubuntu 19.10 64Bit Using Gnome and Gnome Shell 3.34.1-1ubuntu1. ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Bug on Icon View screenshot" https://bugs.launchpad.net/bugs/1849987/+attachment/5300440/+files/Screenshot%20from%202019-10-26%2017-23-21.png -- 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/1849987 Title: empty space when on list view and when back to icon view Status in nautilus package in Ubuntu: New Bug description: Description: Ubuntu 19.10 Release: 19.10 nautilus: Installed: 1:3.34.1-1ubuntu1 Candidate: 1:3.34.1-1ubuntu1 Expected behavior: - (1) Open nautilus in list view OR (2) Open Nautilus in icon view and then switch to list view - List view occupies all the space between the top bar and the bottom. - Switch to icon view - Icon view occupies all the space between the top bar and the bottom. Actual Behavior - (1) Open nautilus in list view OR (2) Open Nautilus in icon view and then switch to list view - List view occupies approximately 55% of the space between the top bar and the bottom. Approximately 45% of the space between the top bar and the bottom is blank (the upmost part). - Switch to icon view - Icon view occupies approximately 55% of the space between the top bar and the bottom. Approximately 45% of the space between the top bar and the bottom is blank (the upmost part). Observations: - The side bar doesn't seem to affect the bug. - By Starting nautilus in icon view the bug doesn't occur. In this case it's only triggered when switching to list view. - There are only 2 known ways to revert the bug: (1) when on icon view, clicking on "Other Locations", and then back to any section. (2) by restarting nautilus. There is no known way to revert the bug in list view. I am on Ubuntu 19.10 64Bit Using Gnome and Gnome Shell 3.34.1-1ubuntu1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1849987/+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 1849930] Re: Additional VPN Breaks First VPN
How is it possible that adding an additional VPN profile can corrupted an "already added and working" vpn? Which packages would be responsible for that type of corruption? Most importantly, short of reinstalling Ubuntu 19.10 what would be a workaround that may remove this corruption? For example, many times in the past, when I've had applications get corrupted, I could usually delete some .hiddenFolder or configuration file, and it would repair the corruption after rebooting. Do any of you know which files would have to be deleted to get my VPN situation back to "fresh install quality" (short of actually reinstalling)? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1849930 Title: Additional VPN Breaks First VPN Status in gnome-control-center: New Status in NetworkManager: New Status in strongSwan: New Status in gnome-control-center package in Ubuntu: New Bug description: When I add only one L2TP VPN profile to gnome-control-center's Network > VPN settings, it works fine. However, if I add a 2nd L2TP VPN, the 2nd L2TP VPN, not only doesn't work, but it corrupts the first L2TP VPN so that it too stops working. Furthermore, if I remove 2nd L2TP VPN profile (that corrupted the first L2TP VPN) this does NOT repair the corruption to the first L2TP VPN, it remains corrupted. Additionally, removing all VPN profiles and re-adding the first one back, doesn't repair the corruption. Rebooting and adding them back doesn't work either. The only thing that works, that I've found, is completely reinstalling Ubuntu 19.10. Please advise better workarounds than reinstalling. Here's what's in the syslog on a failed VPN Connection attempt: Oct 26 02:58:35 workstation5 NetworkManager[1241]: [1572076715.5632] audit: op="connection-activate" uuid="1942cf95-93b1-4e74-a44a-947a46bffb5a" name="L2TP VPN1" pid=3531 uid=1000 result="success" Oct 26 02:58:35 workstation5 NetworkManager[1241]: [1572076715.5702] vpn-connection[0x5642f421c750,1932cf95-91b1-4e85-a44a-498a56befb5a,"L2TP VPN1",0]: Started the VPN service, PID 7273 Oct 26 02:58:35 workstation5 NetworkManager[1241]: [1572076715.5747] vpn-connection[0x5642f421c750,1932cf95-91b1-4e85-a44a-498a56befb5a,"L2TP VPN1",0]: Saw the service appear; activating connection Oct 26 02:58:35 workstation5 NetworkManager[1241]: [1572076715.6566] vpn-connection[0x5642f421c750,1932cf95-91b1-4e85-a44a-498a56befb5a,"L2TP VPN1",0]: VPN connection: (ConnectInteractive) reply received Oct 26 02:58:35 workstation5 NetworkManager[1241]: Stopping strongSwan IPsec failed: starter is not running Oct 26 02:58:37 workstation5 NetworkManager[1241]: Starting strongSwan 5.7.2 IPsec [starter]... Oct 26 02:58:37 workstation5 NetworkManager[1241]: Loading config setup Oct 26 02:58:37 workstation5 NetworkManager[1241]: Loading conn '1942cf95-93b1-4e74-a44a-947a46bffb5a' Oct 26 02:58:37 workstation5 NetworkManager[1241]: found netkey IPsec stack Oct 26 02:58:48 workstation5 NetworkManager[1241]: Stopping strongSwan IPsec... Oct 26 02:58:48 workstation5 NetworkManager[1241]: initiating Main Mode IKE_SA 1942cf95-93b1-4e74-a44a-947a46bffb5a[1] to 49.230.24.121 Oct 26 02:58:48 workstation5 NetworkManager[1241]: generating ID_PROT request 0 [ SA V V V V V ] Oct 26 02:58:48 workstation5 NetworkManager[1241]: sending packet: from 192.168.1.2[500] to 49.230.24.121[500] (236 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: received packet: from 49.230.24.121[500] to 192.168.1.2[500] (156 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: parsed ID_PROT response 0 [ SA V V V V ] Oct 26 02:58:48 workstation5 NetworkManager[1241]: received XAuth vendor ID Oct 26 02:58:48 workstation5 NetworkManager[1241]: received DPD vendor ID Oct 26 02:58:48 workstation5 NetworkManager[1241]: received FRAGMENTATION vendor ID Oct 26 02:58:48 workstation5 NetworkManager[1241]: received NAT-T (RFC 3947) vendor ID Oct 26 02:58:48 workstation5 NetworkManager[1241]: selected proposal: IKE:3DES_CBC/HMAC_SHA1_96/PRF_HMAC_SHA1/MODP_1024 Oct 26 02:58:48 workstation5 NetworkManager[1241]: generating ID_PROT request 0 [ KE No NAT-D NAT-D ] Oct 26 02:58:48 workstation5 NetworkManager[1241]: sending packet: from 192.168.1.2[500] to 49.230.24.121[500] (244 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: received packet: from 49.230.24.121[500] to 192.168.1.2[500] (244 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: parsed ID_PROT response 0 [ KE No NAT-D NAT-D ] Oct 26 02:58:48 workstation5 NetworkManager[1241]: local host is behind NAT, sending keep alives Oct 26 02:58:48 workstation5 NetworkManager[1241]: generating ID_PROT request 0 [ ID HASH ] Oct 26 02:58:48 workstation5 NetworkManager[1241]: sending packet: from 192.168.1.2[4500] to 49.230.24.121[4500] (68 by
[Desktop-packages] [Bug 1244884] Re: URL doesn't open from other application in chromium-browser
As I commented on bug #1849860 (which was marked duplicate of this bug): « it's unclear to me why you'd have a desktop file for chromium in ~/.local/share/applications/ in the first place. If you do, and the Exec line for that file doesn't end with "%u", then that's indeed the cause of the problem. Whoever created that file did it incorrectly. In any case it's not a bug in chromium itself. » ** Changed in: chromium-browser (Ubuntu) Status: Expired => Invalid -- 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/1244884 Title: URL doesn't open from other application in chromium-browser Status in chromium-browser package in Ubuntu: Invalid Bug description: How to generate: Set chromium-browser as default browser. Now open skype (an example application, you can use other). Click on any web link in skpye. A new chromium-browser will open with nothing in address bar. (Situation: someone send me a link (say youtube link), when i click on that chromium-browser open with blank address bar. No web link loaded) Expected: Open new chromium-browser window with link if no browser instance is running otherwise in new tab. Note: If you click on any link in chromium-browser or in chromium- browser webapp than it works fine. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: chromium-browser 30.0.1599.114-0ubuntu1~cm0saucy [modified: usr/share/applications/chromium-browser.desktop] [origin: LP-PPA-cmiller-chromium-browser-stable-daily] ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 CrashDB: ubuntu Date: Sat Oct 26 13:14:39 2013 Desktop-Session: DESKTOP_SESSION = ubuntu XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg XDG_DATA_DIRS = /usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/ Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None ExecutablePath: /usr/lib/chromium-browser/chromium-browser MarkForUpload: True SourcePackage: chromium-browser ThirdParty: True UpgradeStatus: No upgrade log present (probably fresh install) chromium-default: CHROMIUM_FLAGS="" gconf-keys: /desktop/gnome/applications/browser/exec = b'/usr/bin/chromium-browser\n'/desktop/gnome/url-handlers/https/command = b'firefox %s\n'/desktop/gnome/url-handlers/https/enabled = b'true\n'/desktop/gnome/url-handlers/http/command = b'firefox %s\n'/desktop/gnome/url-handlers/http/enabled = b'true\n'/desktop/gnome/session/required_components/windowmanager = b''/apps/metacity/general/compositing_manager = b''/desktop/gnome/interface/icon_theme = b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1244884/+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 1774188] Re: Unlocking the screen takes 5 seconds in Xorg sessions (not so much in Wayland sessions)
I see this, too, on two different machines (one at home, one at work), both desktops with two monitors. Though for me the delay is usually longer then five seconds. The duration of the delay seems to increase with how long the machine's been up since its last reboot. This was not present when I first installed 18.04 a year ago, but seems to have arisen with some subsequent update. -- 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/1774188 Title: Unlocking the screen takes 5 seconds in Xorg sessions (not so much in Wayland sessions) Status in gdm3 package in Ubuntu: Expired Status in gnome-shell package in Ubuntu: Expired Status in mutter package in Ubuntu: Expired Status in xorg-server package in Ubuntu: Expired Bug description: This is a fresh installation of 18.04. After entering the password and pressing enter, it takes 5 seconds for the lock screen to disappear. This problem didn't happen on the same machine with 16.04 or 14.04. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed May 30 15:31:48 2018 InstallationDate: Installed on 2018-05-04 (25 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1774188/+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 1849860] Re: Clicking links in the bash terminal doesn't start navigation
*** This bug is a duplicate of bug 1244884 *** https://bugs.launchpad.net/bugs/1244884 >From comment #22 in bug #1244884, it's unclear to me why you'd have a desktop file for chromium in ~/.local/share/applications/ in the first place. If you do, and the Exec line for that file doesn't end with "%u", then that's indeed the cause of the problem. Whoever created that file did it incorrectly. In any case it's not a bug in chromium itself. -- 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/1849860 Title: Clicking links in the bash terminal doesn't start navigation Status in chromium-browser package in Ubuntu: New Bug description: Upgraded to Ubuntu 19.10, using the new snap Chromium, I click a link in the terminal: EXPECTATION: The clicked link should open in a new tab or window and the navigation to that link should start. ACTUAL RESULT: A new Chromium window opens to the home page and navigation to the clicked link doesn't start. Chromium Version 78.0.3904.70 (Official Build) snap (64-bit) Ubuntu 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1849860/+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 1845302] Re: cannot click on others opened applications while the "application not responding" dialog is opened
same issue i'm facing! thank youhttps://gtalovers.com/";>! -- 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/1845302 Title: cannot click on others opened applications while the "application not responding" dialog is opened Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: Fix Released Status in gnome-shell source package in Eoan: Invalid Status in mutter source package in Eoan: In Progress Bug description: [ Impact ] The "application is not responding" can make the shell hang under X11 [ Test case ] - Start an application (i.e. firefox) - Stop the process killall -STOP firefox - After some moments and interactions with the window the gnome shell dialog to kill the window should pop-up - The shell should be still responsive and you can get the program to run again (killall -CONT firefox) [ Regression potential ] Focus might be wrongly set to the applications or actors and instead be owned by the shell This is uploaded under the gnome MRE, so the fix doesn't need to be explicitly verified. https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1845302/+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 1244884] Re: URL doesn't open from other application in chromium-browser
This bug is still present in Ubuntu 19.10. The workaround to modify the desktop file works though. -- 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/1244884 Title: URL doesn't open from other application in chromium-browser Status in chromium-browser package in Ubuntu: Expired Bug description: How to generate: Set chromium-browser as default browser. Now open skype (an example application, you can use other). Click on any web link in skpye. A new chromium-browser will open with nothing in address bar. (Situation: someone send me a link (say youtube link), when i click on that chromium-browser open with blank address bar. No web link loaded) Expected: Open new chromium-browser window with link if no browser instance is running otherwise in new tab. Note: If you click on any link in chromium-browser or in chromium- browser webapp than it works fine. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: chromium-browser 30.0.1599.114-0ubuntu1~cm0saucy [modified: usr/share/applications/chromium-browser.desktop] [origin: LP-PPA-cmiller-chromium-browser-stable-daily] ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 CrashDB: ubuntu Date: Sat Oct 26 13:14:39 2013 Desktop-Session: DESKTOP_SESSION = ubuntu XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg XDG_DATA_DIRS = /usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/ Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None ExecutablePath: /usr/lib/chromium-browser/chromium-browser MarkForUpload: True SourcePackage: chromium-browser ThirdParty: True UpgradeStatus: No upgrade log present (probably fresh install) chromium-default: CHROMIUM_FLAGS="" gconf-keys: /desktop/gnome/applications/browser/exec = b'/usr/bin/chromium-browser\n'/desktop/gnome/url-handlers/https/command = b'firefox %s\n'/desktop/gnome/url-handlers/https/enabled = b'true\n'/desktop/gnome/url-handlers/http/command = b'firefox %s\n'/desktop/gnome/url-handlers/http/enabled = b'true\n'/desktop/gnome/session/required_components/windowmanager = b''/apps/metacity/general/compositing_manager = b''/desktop/gnome/interface/icon_theme = b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1244884/+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 1849860] Re: Clicking links in the bash terminal doesn't start navigation
*** This bug is a duplicate of bug 1244884 *** https://bugs.launchpad.net/bugs/1244884 ** This bug has been marked a duplicate of bug 1244884 URL doesn't open from other application in chromium-browser -- 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/1849860 Title: Clicking links in the bash terminal doesn't start navigation Status in chromium-browser package in Ubuntu: New Bug description: Upgraded to Ubuntu 19.10, using the new snap Chromium, I click a link in the terminal: EXPECTATION: The clicked link should open in a new tab or window and the navigation to that link should start. ACTUAL RESULT: A new Chromium window opens to the home page and navigation to the clicked link doesn't start. Chromium Version 78.0.3904.70 (Official Build) snap (64-bit) Ubuntu 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1849860/+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 1849907] Re: Add Online Account Nextcloud no Connect button on Unity
** Changed in: gnome-online-accounts (Ubuntu) Importance: Undecided => Medium ** Changed in: gnome-online-accounts (Ubuntu) Status: Incomplete => Confirmed ** Tags added: running-unity -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1849907 Title: Add Online Account Nextcloud no Connect button on Unity Status in gnome-online-accounts package in Ubuntu: Confirmed Bug description: I am trying to add an online account, nextcloud three fields show, server, username and password. There is no Apply or OK button. I cannot add the account. Resizing the window does not help. Fields just get longer, still no buttons. Ubuntu 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1849907/+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 1849950] Re: Window shortcuts maximize, windowed and hide (Super + Up / Down / H) don't work
I fear that GNOME is not the source of this issue. I had a look in the settings and noticed that many shortcuts have been changed from default. I did not do this manually. One suspicion is that it might got changed when changing from Unity to GNOME in an Ubuntu upgrade. After changing those shortcuts back to default, everything worked as expected. However there might have been some problem causing those default values to change. -- 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/1849950 Title: Window shortcuts maximize, windowed and hide (Super + Up / Down / H) don't work Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: New Bug description: Happens on Ubuntu 19.10, and did also not work on Ubuntu 19.04 (and probably also previous versions), if I recall correctly. I am not sure, whether this is an upstream bug of GNOME or just Ubuntu related. Bug report for GNOME: https://gitlab.gnome.org/GNOME/gnome- shell/issues/1829 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1849950/+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 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
Well after commenting out the lines in /etc/gdm3/custom.conf and rebooting it worked for me. But currently i can not reenable the automatic login again. No matter what i do. Remove the comments, enable the option in the users menu. nothing works. even enabling the option in the users menu does little and after clicking away it does not save it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. Status in gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in gdm3 source package in Eoan: Confirmed Status in gnome-session source package in Eoan: Confirmed Status in gnome-shell source package in Eoan: Confirmed Bug description: I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago) dmi.bios.date: 01/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: Default string dmi.board.name: H270I GAMING PRO AC (MS-7A67) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7A67 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+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.launchp
[Desktop-packages] [Bug 1841953] Re: Bionic ⋅ SuperTuxKart ⋅ Flickering shadows ⋅ Haswell i915
try newer mesa on ppa:ubuntu-x-swat/updates ** Changed in: mesa (Ubuntu) Status: New => Incomplete ** No longer affects: xserver-xorg-video-intel ** No longer affects: mesa -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1841953 Title: Bionic ⋅ SuperTuxKart ⋅ Flickering shadows ⋅ Haswell i915 Status in mesa package in Ubuntu: Incomplete Status in supertuxkart package in Ubuntu: New Bug description: Hi, for few weeks now, I've noticed a big change in graphic performance while playing famous SuperTuxKart on ubuntu bionic : shadows are flickering, all over the screen, it's a big pain for eyes ( and wonder what would happen for epileptic people ). My computer is : Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz with 16Go ram and Haswell integrated graphics. coeur-noir@asgard:~$ lspci -k | grep -A 2 -i "VGA" 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller (rev 06) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller Kernel driver in use: i915 coeur-noir@asgard:~$ sudo lshw -c video *-display description: VGA compatible controller produit: Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller fabriquant: Intel Corporation identifiant matériel: 2 information bus: pci@:00:02.0 version: 06 bits: 64 bits horloge: 33MHz fonctionnalités: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 ressources: irq:26 mémoire:f780-f7bf mémoire:e000-efff portE/S:f000(taille=64) mémoire:c-d coeur-noir@asgard:~$ My Ubuntu Budgie 18.04 is : coeur-noir@asgard:~$ lsb_release -rd Description: Ubuntu 18.04.3 LTS Release: 18.04 coeur-noir@asgard:~$ uname -a Linux asgard 5.0.0-23-generic #24~18.04.1-Ubuntu SMP Mon Jul 29 16:12:28 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux coeur-noir@asgard:~$ mesa packages are : coeur-noir@asgard:~$ dpkg -l | grep mesa ii libegl-mesa0:amd64 19.0.8-0ubuntu0~18.04.1 amd64free implementation of the EGL API -- Mesa vendor library ii libegl1-mesa:amd64 19.0.8-0ubuntu0~18.04.1 amd64transitional dummy package ii libgl1-mesa-dri:amd64 19.0.8-0ubuntu0~18.04.1 amd64free implementation of the OpenGL API -- DRI modules ii libgl1-mesa-dri:i38619.0.8-0ubuntu0~18.04.1 i386 free implementation of the OpenGL API -- DRI modules ii libgl1-mesa-glx:amd64 19.0.8-0ubuntu0~18.04.1 amd64transitional dummy package ii libgl1-mesa-glx:i38619.0.8-0ubuntu0~18.04.1 i386 transitional dummy package ii libglapi-mesa:amd64 19.0.8-0ubuntu0~18.04.1 amd64free implementation of the GL API -- shared library ii libglapi-mesa:i386 19.0.8-0ubuntu0~18.04.1 i386 free implementation of the GL API -- shared library ii libgles2-mesa:amd64 19.0.8-0ubuntu0~18.04.1 amd64transitional dummy package ii libglu1-mesa:amd64 9.0.0-2.1build1 amd64Mesa OpenGL utility library (GLU) ii libglu1-mesa:i386 9.0.0-2.1build1 i386 Mesa OpenGL utility library (GLU) ii libglx-mesa0:amd64 19.0.8-0ubuntu0~18.04.1 amd64free implementation of the OpenGL API -- GLX vendor library ii libglx-mesa0:i386 19.0.8-0ubuntu0~18.04.1 i386 free implementation of the OpenGL API -- GLX vendor library ii libosmesa6:amd6419.0.8-0ubuntu0~18.04.1 amd64Mesa Off-screen rendering extension ii libosmesa6:i386 19.0.8-0ubuntu0~18.04.1 i386 Mesa Off-screen rendering extension ii libwayland-egl1-mesa:amd64 19.0.8-0ubuntu0~18.04.1 amd64transitional dummy package ii mesa-utils 8.4.0-1 amd64Miscellaneous Mesa GL utilities ii mesa-utils-extra8.4.0-1 amd64Miscellaneous Mesa utilies (opengles, egl) ii mesa-va-drivers:amd64 19.0.8-0ubuntu0~18.04.1
[Desktop-packages] [Bug 1849615] Re: WebRTC-related crashes
** Bug watch added: Mozilla Bugzilla #1581193 https://bugzilla.mozilla.org/show_bug.cgi?id=1581193 -- 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/1849615 Title: WebRTC-related crashes Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: New Bug description: In Mozilla we've detected a spike of crashes in the Ubuntu-packaged version of Firefox 69.0.x. All the crashes are happening in the WebRTC code and specifically libc's FD_SET, FD_CLR and FD_ISSET range- checking safety is causing an abort. Is it possible that Firefox is being built with a FD_SETSIZE value that's different from what's used in libc? To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1849615/+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 1849907] Re: Add Online Account Nextcloud no Apply button
I have tried every setting I can find. The buttons remain invisible. I run Ubuntu 19.10 with default unity desktop. However.. when I changed to "Ubuntu on Wayland" in the login screen.. the buttons appeared. So, my problem with the "Online Accounts" is solved with a work-around, but the problem in Unity remains. ** Summary changed: - Add Online Account Nextcloud no Apply button + Add Online Account Nextcloud no Connect button on Unity -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1849907 Title: Add Online Account Nextcloud no Connect button on Unity Status in gnome-online-accounts package in Ubuntu: Incomplete Bug description: I am trying to add an online account, nextcloud three fields show, server, username and password. There is no Apply or OK button. I cannot add the account. Resizing the window does not help. Fields just get longer, still no buttons. Ubuntu 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1849907/+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 1849615]
(In reply to Gabriele Svelto [:gsvelto] from comment #2) > I did some further digging and this is happening all over the place but > mostly in code we don't control. It's always `select()`'s fault though. > Daniel, this code is different from upstream WebRTC (which is also using > `select()` but in other places), is there a reason for this? I can cook up a > patch to switch this code to `poll()` instead but I wonder if it's the right > thing to do or if this should be fixed upstream first. Hi Gabriele, this code is our local modification to webrtc.org that we have never merged upstream. As such, feel free to rewrite it to use poll() if that will fix things. I'm not the original author, I just happened to do the last upstream merge, so I can't comment on why select was chosen rather than poll. :jesup might know if you want to follow up with him. One thing to be careful of is that this code is handling cameras being plugged and unplugged which is not something we have coverage for in automation, so you'll have to do some manual testing of your changes. The STR from https://bugzilla.mozilla.org/show_bug.cgi?id=1581193#c0 might be helpful here. -- 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/1849615 Title: WebRTC-related crashes Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: New Bug description: In Mozilla we've detected a spike of crashes in the Ubuntu-packaged version of Firefox 69.0.x. All the crashes are happening in the WebRTC code and specifically libc's FD_SET, FD_CLR and FD_ISSET range- checking safety is causing an abort. Is it possible that Firefox is being built with a FD_SETSIZE value that's different from what's used in libc? To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1849615/+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 1849615]
(In reply to Dan Minor [:dminor] from comment #3) > Hi Gabriele, this code is our local modification to webrtc.org that we have > never merged upstream. As such, feel free to rewrite it to use poll() if that > will fix things. I'm not the original author, I just happened to do the last > upstream merge, so I can't comment on why select was chosen rather than poll. > :jesup might know if you want to follow up with him. > > One thing to be careful of is that this code is handling cameras being > plugged and unplugged which is not something we have coverage for in > automation, so you'll have to do some manual testing of your changes. The STR > from https://bugzilla.mozilla.org/show_bug.cgi?id=1581193#c0 might be helpful > here. Thanks, I'll try to cook up a patch tomorrow. I must have a USB camera sitting around somewhere so testing shouldn't be a problem. -- 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/1849615 Title: WebRTC-related crashes Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: New Bug description: In Mozilla we've detected a spike of crashes in the Ubuntu-packaged version of Firefox 69.0.x. All the crashes are happening in the WebRTC code and specifically libc's FD_SET, FD_CLR and FD_ISSET range- checking safety is causing an abort. Is it possible that Firefox is being built with a FD_SETSIZE value that's different from what's used in libc? To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1849615/+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 1849965] [NEW] I got stuck in a Login-Loop. The solution with the .Xauthority permission would not fix it. Next i read about a lightdm bug. Since new ubuntu is using not lightd
Public bug reported: New upgrade failed with initial upgrade and i had to boot-repair to get to the normal ubuntu login window. The button Automatic Login in the settings does not work either... Using Ubuntu 19.10 gdm3: Installed: 3.34.1-1ubuntu1 Candidate: 3.34.1-1ubuntu1 Version table: *** 3.34.1-1ubuntu1 500 500 http://ch.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status After a few Logins the bug reappeared and i had to reinstall the gdm3 package once again. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gdm3 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 26 16:42:18 2019 InstallationDate: Installed on 2018-09-23 (398 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1849965 Title: I got stuck in a Login-Loop. The solution with the .Xauthority permission would not fix it. Next i read about a lightdm bug. Since new ubuntu is using not lightdm but gdm3 i sudo apt-get purge gdm3 . Then reinstalled. After that i could login successfully. Status in gdm3 package in Ubuntu: New Bug description: New upgrade failed with initial upgrade and i had to boot-repair to get to the normal ubuntu login window. The button Automatic Login in the settings does not work either... Using Ubuntu 19.10 gdm3: Installed: 3.34.1-1ubuntu1 Candidate: 3.34.1-1ubuntu1 Version table: *** 3.34.1-1ubuntu1 500 500 http://ch.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status After a few Logins the bug reappeared and i had to reinstall the gdm3 package once again. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gdm3 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 26 16:42:18 2019 InstallationDate: Installed on 2018-09-23 (398 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1849965/+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 1849947] Re: Dell XPS 13 (7390) Display Flickering - 19.10
please test with latest drm-tip kernel from https://kernel.ubuntu.com/~kernel-ppa/mainline/ ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Incomplete -- 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/1849947 Title: Dell XPS 13 (7390) Display Flickering - 19.10 Status in linux package in Ubuntu: Incomplete Bug description: Hi there, I recently purchased a Dell XPS 13 7390 (Developer Edition). I decided to replace 18.4 LTS with 19.10 and so far it has been pretty smooth. However, there is one issue which occurs frequently whereby the display flickers and becomes unusable. The best way to describe the appearance is that the image becomes heavily distorted. Sometimes it only happens for a split second, other times it is permanently distorted. When this happens, simply closing the laptop lip and re-opening seems to put the display back into it's correct state. I didn't experience this issue on 18.04 LTS which is why I believe it's a Software Bug within 19.10. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Oct 26 11:11:43 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0962] InstallationDate: Installed on 2019-10-25 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. XPS 13 7390 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/23/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.3 dmi.board.name: 0G2D0W dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.3:bd08/23/2019:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0G2D0W:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 dmi.product.sku: 0962 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849947/+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 1841953] Re: Bionic ⋅ SuperTuxKart ⋅ Flickering shadows ⋅ Haswell i915
Anyway remember I have no flickering shadows problem when booting the same computer on 16.04. So it's a regression but how narrow down any culprit ? ** Also affects: supertuxkart (Ubuntu) Importance: Undecided Status: New ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1841953 Title: Bionic ⋅ SuperTuxKart ⋅ Flickering shadows ⋅ Haswell i915 Status in Mesa: New Status in xf86-video-intel: New Status in mesa package in Ubuntu: New Status in supertuxkart package in Ubuntu: New Bug description: Hi, for few weeks now, I've noticed a big change in graphic performance while playing famous SuperTuxKart on ubuntu bionic : shadows are flickering, all over the screen, it's a big pain for eyes ( and wonder what would happen for epileptic people ). My computer is : Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz with 16Go ram and Haswell integrated graphics. coeur-noir@asgard:~$ lspci -k | grep -A 2 -i "VGA" 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller (rev 06) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller Kernel driver in use: i915 coeur-noir@asgard:~$ sudo lshw -c video *-display description: VGA compatible controller produit: Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller fabriquant: Intel Corporation identifiant matériel: 2 information bus: pci@:00:02.0 version: 06 bits: 64 bits horloge: 33MHz fonctionnalités: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 ressources: irq:26 mémoire:f780-f7bf mémoire:e000-efff portE/S:f000(taille=64) mémoire:c-d coeur-noir@asgard:~$ My Ubuntu Budgie 18.04 is : coeur-noir@asgard:~$ lsb_release -rd Description: Ubuntu 18.04.3 LTS Release: 18.04 coeur-noir@asgard:~$ uname -a Linux asgard 5.0.0-23-generic #24~18.04.1-Ubuntu SMP Mon Jul 29 16:12:28 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux coeur-noir@asgard:~$ mesa packages are : coeur-noir@asgard:~$ dpkg -l | grep mesa ii libegl-mesa0:amd64 19.0.8-0ubuntu0~18.04.1 amd64free implementation of the EGL API -- Mesa vendor library ii libegl1-mesa:amd64 19.0.8-0ubuntu0~18.04.1 amd64transitional dummy package ii libgl1-mesa-dri:amd64 19.0.8-0ubuntu0~18.04.1 amd64free implementation of the OpenGL API -- DRI modules ii libgl1-mesa-dri:i38619.0.8-0ubuntu0~18.04.1 i386 free implementation of the OpenGL API -- DRI modules ii libgl1-mesa-glx:amd64 19.0.8-0ubuntu0~18.04.1 amd64transitional dummy package ii libgl1-mesa-glx:i38619.0.8-0ubuntu0~18.04.1 i386 transitional dummy package ii libglapi-mesa:amd64 19.0.8-0ubuntu0~18.04.1 amd64free implementation of the GL API -- shared library ii libglapi-mesa:i386 19.0.8-0ubuntu0~18.04.1 i386 free implementation of the GL API -- shared library ii libgles2-mesa:amd64 19.0.8-0ubuntu0~18.04.1 amd64transitional dummy package ii libglu1-mesa:amd64 9.0.0-2.1build1 amd64Mesa OpenGL utility library (GLU) ii libglu1-mesa:i386 9.0.0-2.1build1 i386 Mesa OpenGL utility library (GLU) ii libglx-mesa0:amd64 19.0.8-0ubuntu0~18.04.1 amd64free implementation of the OpenGL API -- GLX vendor library ii libglx-mesa0:i386 19.0.8-0ubuntu0~18.04.1 i386 free implementation of the OpenGL API -- GLX vendor library ii libosmesa6:amd6419.0.8-0ubuntu0~18.04.1 amd64Mesa Off-screen rendering extension ii libosmesa6:i386 19.0.8-0ubuntu0~18.04.1 i386 Mesa Off-screen rendering extension ii libwayland-egl1-mesa:amd64 19.0.8-0ubuntu0~18.04.1 amd64transitional dummy package ii mesa-utils 8.4.0-1 amd64Miscellaneous Mesa GL utilities ii mesa-utils-extra8.4.0-1
[Desktop-packages] [Bug 1836979] Re: Kodi crashes with “nouveau_vp3_video_buffer_create: Assertion `templat->interlaced' failed”
could you test with ppa:ubuntu-x-swat/updates which has a newer mesa backported from eoan? ** Changed in: mesa (Ubuntu Bionic) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1836979 Title: Kodi crashes with “nouveau_vp3_video_buffer_create: Assertion `templat->interlaced' failed” Status in mesa package in Ubuntu: Confirmed Status in mesa source package in Bionic: Incomplete Bug description: Buggy as Kodi is, this seems to be a problem specifically with mesa- va-drivers. Kodi has worked just fine on my system, as recently as July 6th of this year, but yesterday (July 16) I tried Kodi again: I got a blank screen and a pause for a few moments, followed by an unceremonious crash-to-desktop. This happens every time I start Kodi, now. If I run it through the command-line, I get this: libva info: VA-API version 1.1.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/nouveau_drv_video.so libva info: Found init function __vaDriverInit_1_1 libva info: va_openDriver() returns 0 kodi-x11: ../src/gallium/drivers/nouveau/nouveau_vp3_video.c:91: nouveau_vp3_video_buffer_create: Assertion `templat->interlaced' failed. Aborted (core dumped) I’ve been using the same version of Kodi (“18.3 Git:20190621-89472b7”, package version 2:18.3+git20190621.1610-final-0bionic, from the Team- XBMC PPA) since its release in June, but in between July 6th and 16th, I did upgrade the Mesa packages, from 18.2.8-0ubuntu0~18.04.2 19.0.2-1ubuntu1.1~18.04.1. If I downgrade the “mesa-va-drivers” package to 18.0.0~rc5-1ubuntu1 (the version in the base, non-updates Bionic repository), however, Kodi works again, without even requiring me to restart my machine. So, this is likely a problem with “mesa-va- drivers”. I tried looking in Xorg.0.log: [ 17185.557] (II) NOUVEAU(0): EDID vendor "SEC", prod id 12620 [ 17185.557] (II) NOUVEAU(0): Printing DDC gathered Modelines: [ 17185.558] (II) NOUVEAU(0): Modeline "1366x768"x0.0 72.33 1366 1414 1446 1526 768 770 775 790 -hsync -vsync (47.4 kHz eP) …that’s all that appears in the log when I try to load Kodi and a crash happens. I’m using Ubuntu MATE 18.04.2 LTS 64-bit on a Compaq Presario CQ60; if you need more information, I’ve attached a hardinfo report, too. I hope this bug can get fixed, soon. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1836979/+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 1837170] Re: Kodi package crash after the update of libdrm-amdgpu1
thanks for confirming that 19.0.8-0ubuntu0~18.04.2 fixed it, the reason was due to meson not using -DDEBUG before, and it is forced in this version and should avoid known assertions in the drivers since you have some other issue now, you should file a new bug and against the kernel if it's a regression there ** Changed in: mesa (Ubuntu) Status: Incomplete => Fix Released ** Changed in: mesa (Ubuntu) Assignee: Timo Aaltonen (tjaalton) => (unassigned) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1837170 Title: Kodi package crash after the update of libdrm-amdgpu1 Status in mesa package in Ubuntu: Fix Released Bug description: Greetings, The last update of libdrm-amdgpu1 caused a bug on Kodi package, making it to crash after loading any video or reproduce a black image. Version: 2.4.97-1ubuntu1~18.04.12019-07-03 15:07:54 UTC libdrm (2.4.97-1ubuntu1~18.04.1) bionic; urgency=medium * Backport to bionic for 18.04.3 HWE stack update. (LP: #1824111) -- Timo Aaltonen Wed, 10 Apr 2019 13:54:06 +0300 Kodi gives this error: #3 0x7f47676c60aa in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f47676c5dd7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so Repeated several times #3 0x7f475ce2c5a6 in ?? () from /usr/lib/x86_64-linux-gnu/libLLVM-8.so.1 #4 0x7f475ce2c425 in ?? () from /usr/lib/x86_64-linux-gnu/libLLVM-8.so.1 Team-Kodi stated these errors are in relation to 'Not supported GPU drivers', when Kodi can't find these files. I've found the cause, and a temporary solution: This bug was caused after an update for the latest version of libdrm- amdgpu1 2.4.97-1ubuntu1~18.04.1 So I grabbed the previous version from https://mirror.transip.net/ubuntu/ubuntu/pool/main/libd/libdrm/ installed libdrm-amdgpu1_2.4.95-1~18.04.1_amd64.deb and now Kodi returns. I created a bug report, the problem affects multiple users. https://bugs.launchpad.net/ubuntu/+source/kodi/+bug/1836828 We have a PointRelease coming soon, would we have time to fix this package? Thank you for your assistance. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1837170/+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 1849950] Re: Window shortcuts maximize, windowed and hide (Super + Up / Down / H) don't work
** Changed in: gnome-shell Status: Unknown => New -- 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/1849950 Title: Window shortcuts maximize, windowed and hide (Super + Up / Down / H) don't work Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: New Bug description: Happens on Ubuntu 19.10, and did also not work on Ubuntu 19.04 (and probably also previous versions), if I recall correctly. I am not sure, whether this is an upstream bug of GNOME or just Ubuntu related. Bug report for GNOME: https://gitlab.gnome.org/GNOME/gnome- shell/issues/1829 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1849950/+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 1754872] Re: apt install xubuntu-desktop does not resolve dependencies properly
I've added this to the 20.04 development blueprint, so let's revisit and discuss. If we can't solve the problem with packaging, let's document the mini.iso installation process so others have an easier time. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1754872 Title: apt install xubuntu-desktop does not resolve dependencies properly Status in apt package in Ubuntu: Invalid Status in gnome-control-center package in Ubuntu: Invalid Status in indicator-datetime package in Ubuntu: Invalid Status in xfce4-session package in Ubuntu: Fix Released Status in xubuntu-meta package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Install `xubuntu-desktop` meta package on 18.04 LTS 2. Login to session 3a. Click on clock indicator on panel, select "Time & Date Settings" 3b. Click on Gear, select "About this Computer" or "System Settings" 3c. Click on keyboard layout indicator, select "Text Entry Settings" Expected results: xfce-oriented control center is opened Actual results: gnome-control-center is opened, but with empty window. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xubuntu-desktop 2.223 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Mar 10 21:10:11 2018 SourcePackage: xubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1754872/+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 1849955] [NEW] Display jumps on dock/undock and on volume/brightness overlay
Public bug reported: I often dock/undock my laptop, introducing two additional displays. Every time I dock/undock (and when using the volume/brightness controls after undocking) the display jumps about. Here's a video showing it. https://www.youtube.com/watch?v=HfhPrh2y7Y8 Steps to reproduce. * Plug laptop into a docking station (possibly just attach an external display) * Configure the desktop running spanning all displays * Remove the external display / undock * Observe the laptop desktop jump around * Use the brightness or volume adjust keys * Observe the laptop desktop jump around Expected behaviour * The desktop should not jump around ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 26 14:15:11 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-02-04 (628 days ago) InstallationMedia: neon userlts "Xenial" - Build amd64 LIVE Binary 20180202-11:07 RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-09-19 (36 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- 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/1849955 Title: Display jumps on dock/undock and on volume/brightness overlay Status in gnome-shell package in Ubuntu: New Bug description: I often dock/undock my laptop, introducing two additional displays. Every time I dock/undock (and when using the volume/brightness controls after undocking) the display jumps about. Here's a video showing it. https://www.youtube.com/watch?v=HfhPrh2y7Y8 Steps to reproduce. * Plug laptop into a docking station (possibly just attach an external display) * Configure the desktop running spanning all displays * Remove the external display / undock * Observe the laptop desktop jump around * Use the brightness or volume adjust keys * Observe the laptop desktop jump around Expected behaviour * The desktop should not jump around ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 26 14:15:11 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-02-04 (628 days ago) InstallationMedia: neon userlts "Xenial" - Build amd64 LIVE Binary 20180202-11:07 RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-09-19 (36 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1849955/+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 1843912] Re: Update to 9.0.0 next cycle
auto-synced to 20.04 ** Changed in: qpdf (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to qpdf in Ubuntu. https://bugs.launchpad.net/bugs/1843912 Title: Update to 9.0.0 next cycle Status in qpdf package in Ubuntu: Fix Released Bug description: The new version has feature and small incompatibilities http://qpdf.sourceforge.net/files/qpdf-manual.html#ref.release-notes%3E To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qpdf/+bug/1843912/+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 1849907] Re: Add Online Account Nextcloud no Apply button
On 2019-10-26 11:00, Magnus Pernemark wrote: > I think I have changed how menues and/or title bar of window should > show. I will look into that. Yeah, please do. I keep the "Incomplete" status of this bug until you have provided some details. It would be good if you could figure out exactly which changed setting(s) broke the window. > Regardless, it is not a good implementation if submit buttons > disapear if you change system settings of windows. The function of a > window should remain, even if the theam of the desktop change. Fair point. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1849907 Title: Add Online Account Nextcloud no Apply button Status in gnome-online-accounts package in Ubuntu: Incomplete Bug description: I am trying to add an online account, nextcloud three fields show, server, username and password. There is no Apply or OK button. I cannot add the account. Resizing the window does not help. Fields just get longer, still no buttons. Ubuntu 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1849907/+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 1849950] Re: Window shortcuts maximize, windowed and hide (Super + Up / Down / H) don't work
** Package changed: ubuntu => gnome-shell (Ubuntu) ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #1829 https://gitlab.gnome.org/GNOME/gnome-shell/issues/1829 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/issues/1829 Importance: Unknown Status: Unknown ** Tags added: disco eoan -- 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/1849950 Title: Window shortcuts maximize, windowed and hide (Super + Up / Down / H) don't work Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: New Bug description: Happens on Ubuntu 19.10, and did also not work on Ubuntu 19.04 (and probably also previous versions), if I recall correctly. I am not sure, whether this is an upstream bug of GNOME or just Ubuntu related. Bug report for GNOME: https://gitlab.gnome.org/GNOME/gnome- shell/issues/1829 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1849950/+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 1849950] [NEW] Window shortcuts maximize, windowed and hide (Super + Up / Down / H) don't work
You have been subscribed to a public bug: Happens on Ubuntu 19.10, and did also not work on Ubuntu 19.04 (and probably also previous versions), if I recall correctly. I am not sure, whether this is an upstream bug of GNOME or just Ubuntu related. Bug report for GNOME: https://gitlab.gnome.org/GNOME/gnome- shell/issues/1829 ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment keyboard shortcuts tiling window -- Window shortcuts maximize, windowed and hide (Super + Up / Down / H) don't work https://bugs.launchpad.net/bugs/1849950 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell 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 1741074] Re: [snap] chrome-gnome-shell extension fails to detect native host connector
zebul666, please take time to read: https://discourse.ubuntu.com/t/intent-to-provide-chromium-as-a-snap-only/5987 https://discourse.ubuntu.com/t/please-test-chromium-snap-as-a-replacement-for-the-deb/7978 https://discourse.ubuntu.com/t/call-for-testing-chromium-browser-deb-to-snap-transition/11179 Those threads should answer your questions as to why the Chromium browser will only be provided as a snap in Ubuntu 19.10 and eventually in all supported releases of Ubuntu. -- 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/1741074 Title: [snap] chrome-gnome-shell extension fails to detect native host connector Status in chromium-browser package in Ubuntu: Triaged Bug description: (initially reported at https://forum.snapcraft.io/t/chrome-gnome- shell-does-not-work-with-chromium-snap/3377) See attached screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1741074/+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 1841774] Re: gnome-shell freezes and continuously logs "JS ERROR: TypeError: null has no properties" in _addWindowEffect from vfunc_show (both in closeDialog.js)
The bug has been reported upstream and looks like the same bug https://gitlab.gnome.org/GNOME/gnome-shell/issues/1607 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #1607 https://gitlab.gnome.org/GNOME/gnome-shell/issues/1607 -- 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/1841774 Title: gnome-shell freezes and continuously logs "JS ERROR: TypeError: null has no properties" in _addWindowEffect from vfunc_show (both in closeDialog.js) Status in gnome-shell package in Ubuntu: Incomplete Bug description: I was closing the dialog of the "software and updates" tools (I was checking the repositories and ppa), but the entire desktop went into freeze, no mouse movement, at the click no action, I pressed the keys "ctrl + alt + f3 "and I went into a tty session, from there I recorded the logs via:" journalctl -f> log ", and I restarted. This is one part of the log, but it seems to repeat itself, I have attached a file with a longer log. -- Logs begin at Tue 2019-02-19 00:29:40 CET. -- ago 28 13:41:35 emanuc gnome-shell[2747]: JS ERROR: TypeError: null has no properties _addWindowEffect@resource:///org/gnome/shell/ui/closeDialog.js:74:13 vfunc_show@resource:///org/gnome/shell/ui/closeDialog.js:145:9 ago 28 13:41:35 emanuc gnome-shell[2747]: JS ERROR: TypeError: null has no properties _addWindowEffect@resource:///org/gnome/shell/ui/closeDialog.js:74:13 vfunc_show@resource:///org/gnome/shell/ui/closeDialog.js:145:9 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.33.91-1ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8 Uname: Linux 5.2.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 28 14:51:01 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-02-18 (190 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190130) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.33.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1841774/+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 1741074] Re: [snap] chrome-gnome-shell extension fails to detect native host connector
How and why that snap has been rolled out in 19.10 while we have less feature with it ? Note: I don't like snap. This bug is another example why. Moreover nobody cares to fix this. If it is even possible... -- 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/1741074 Title: [snap] chrome-gnome-shell extension fails to detect native host connector Status in chromium-browser package in Ubuntu: Triaged Bug description: (initially reported at https://forum.snapcraft.io/t/chrome-gnome- shell-does-not-work-with-chromium-snap/3377) See attached screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1741074/+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 1841774] Re: gnome-shell freezes and continuously logs "JS ERROR: TypeError: null has no properties" in _addWindowEffect from vfunc_show (both in closeDialog.js)
I have this problem as well. Virgin/Clean install of Eoan Desktop install in a KVM virtual machine. Install package cqrlog, which has a long startup time and usually causes the "not responding" dialog to raise, but can be dismissed. Under Eoan, the "CQRLOG is not responding" dialog cannot be dismissed - both "Force Quit" and "Wait" are greyed out and cannot be selected. gnome-shell then runs to 100% cpu utilisation (one thread/core) and repeatedly logs: gnome-shell[4157]: JS ERROR: TypeError: null has no properties#012_addWindowEffect@resource:///org/gnome/shell/ui/closeDialog.js:74:13#012vfunc_show@resource:///org/gnome/shell/ui/closeDialog.js:145:9 in syslog. Killing gnome-shell clears the "not responding" dialog. Not this is a virgin install to debug this problem, no extensions or anything else installed (except mariadb-server and cqrlog). -- 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/1841774 Title: gnome-shell freezes and continuously logs "JS ERROR: TypeError: null has no properties" in _addWindowEffect from vfunc_show (both in closeDialog.js) Status in gnome-shell package in Ubuntu: Incomplete Bug description: I was closing the dialog of the "software and updates" tools (I was checking the repositories and ppa), but the entire desktop went into freeze, no mouse movement, at the click no action, I pressed the keys "ctrl + alt + f3 "and I went into a tty session, from there I recorded the logs via:" journalctl -f> log ", and I restarted. This is one part of the log, but it seems to repeat itself, I have attached a file with a longer log. -- Logs begin at Tue 2019-02-19 00:29:40 CET. -- ago 28 13:41:35 emanuc gnome-shell[2747]: JS ERROR: TypeError: null has no properties _addWindowEffect@resource:///org/gnome/shell/ui/closeDialog.js:74:13 vfunc_show@resource:///org/gnome/shell/ui/closeDialog.js:145:9 ago 28 13:41:35 emanuc gnome-shell[2747]: JS ERROR: TypeError: null has no properties _addWindowEffect@resource:///org/gnome/shell/ui/closeDialog.js:74:13 vfunc_show@resource:///org/gnome/shell/ui/closeDialog.js:145:9 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.33.91-1ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8 Uname: Linux 5.2.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 28 14:51:01 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-02-18 (190 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190130) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.33.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1841774/+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 1849081] Re: ZSH shells break Login screen
More updates. There was an issue with Powerlevel, at least as documented here. https://github.com/romkatv/powerlevel10k/issues/280 However, the issue seems to be lower level. An important issue seems to happen here: include this line at the top of .bashrc when using zsh ``` exec zsh ``` It seems this somehow breaks the login shell. I was able to reproduce this on my other laptop with 18.04. As long as that line is not there, the latest version of ZSH + oh_my_zsh + Powerlevel10k are working fine. This bug may be closed at your discretion, but it seems that there is benefit in somehow find out how to avoid this breaking in such case . -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1849081 Title: ZSH shells break Login screen Status in gnome-keyring package in Ubuntu: New Bug description: There's a bug that affects gnome-keyring, and i'll describe the steps i've done to reproduce it twice, although i don't have full details as to what exactly is causing it. Issue can be summarized as follows: On Ubuntu 19.10, but not at least 18.04 (another computer i have using the older release), there's an issue that prevents the user to login to a gnome session The issue shows up when checking the session manager: ``` service gdm3 status Process: ExecStartPre: /usr/share/gdm/generate-config (code=exited,status=0/SUCCESS) Process: ExecStartPre: /usr/lib/gdm3/gdm-wait-for-drm (code=exited,status=0/SUCCESS) ... gdm-password: gkr-pam: unable to local control file ``` Relevant components: * gdm3 3.34.1-1 * gnome-shell 3.34.1-1 * gnome-keyring 3.34.0-1 * zsh 5.77.1-ubuntu2 This does not occur on a fresh installation of Ubuntu. It only happens once some of these tools are installed: * zsh (ubuntu package https://packages.ubuntu.com/eoan/zsh , manually change shell for user) - https://askubuntu.com/questions/131823/how-to-make-zsh-the-default-shell * oh-my-zsh (brings in lots of plugins, although only git was sourced) - https://github.com/robbyrussell/oh-my-zsh/wiki/Installing-ZSH * powerlevel10k (shell theme ) - https://github.com/romkatv/powerlevel10k The tools would appear to work fine, until you reboot the machine, and are asked to login, at which point gkr-pam complains that it can't locate control file. Unfortunately i don't have better details because eventually i broke so much my login that i decided to reinstall the system from scratch. Upon installation, i started from fresh, with no zsh, and everything worked. Once zsh was installed, it will no longer work. A fix for this was to revert to bash shell. The key change was to no include this line at the top of .bashrc ``` #exec zsh ``` So i can confirm the issue is there, but that's as far as i got after several hours of investigations. I appreciate that this bug may not be a gnome-keyring specific bug, but seems that its the one been affected anyways. https://gitlab.gnome.org/GNOME/gnome-keyring/issues/28 https://gitlab.gnome.org/GNOME/gnome-keyring/issues/26 https://github.com/GNOME/gnome-keyring/blob/master/pam/gkr-pam-module.c#L676 https://github.com/GNOME/gnome-keyring/blob/master/pam/gkr-pam-module.c#L847 https://github.com/GNOME/gnome-keyring/commit/443a821cba105e8f277828a67b3d019b67f1324a https://github.com/GNOME/gnome-keyring/commit/b22d058a055ec3e0f31ae16417f16b42baadb42f https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1817128 https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1818616 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1849081/+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 1573959] Re: On-screen text disappears after suspend
I have the same issue. $ uname -a Linux desk 5.0.0-32-generic #34~18.04.2-Ubuntu SMP Thu Oct 10 10:36:02 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux $ lspci -nn | grep VGA 00:02.0 VGA compatible controller [0300]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0402] (rev 06) $ lsb_release -d Description:Ubuntu 18.04.3 LTS -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1573959 Title: On-screen text disappears after suspend Status in linux-lts-xenial package in Ubuntu: Confirmed Status in xserver-xorg-video-intel package in Ubuntu: Confirmed Bug description: After resuming from a suspend, almost all text on screen is not visible. This includes menu items, text in all three boxes (list of folders, list of e-mails, e-mail body) in Thunderbird (with the curious exception of "ffl" in the File menu), top menu in Chromium (but not the menu obtained by pressing the hamburger button), and the menus produced by clicking items in the system tray. Also, the apport dialog had no text except for a few capital letters. WORKAROUND / 'FIX' (added on March 9, 2017) Several people have mentioned upgrading to kernel 4.8 or higher solves the issue. As per #81, you can easily install kernel 4.8 (if you're on Ubuntu 16.04, that is) by running sudo apt install linux-generic-hwe-16.04 If you are still experiencing this issue after upgrading to kernel 4.8, please share your system details in the comments. ADDITIONAL INFORMATION: * initctl restart unity-panel-service restarts the panel, but the text is still missing * suspend and resume does not fix the issue * Logging out fixes the issue * Other affected applications: ** Chromium file select dialog ** Terminal (entire window) ** ttys 1-6 (Ctrl+Alt+F1, etc.) ** Document viewer (menus) ** Software Updater ** Rhythmbox ** The dialog that appears when you take a screenshot with Ctrl+Alt+PrtSc ** ubuntu-bug ** Nautilus ** LibreOffice Calc (spreadsheet text contents) ** Firefox * Unity dash is not affected. * Skype is not affected. * Mousing over a button in a dialog correctly shows the text. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unity 7.4.0+16.04.20160415-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 BootLog: CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,gnomecompat,imgpng,place,move,resize,vpswitch,snap,regex,grid,mousepoll,unitymtgrabhandles,animation,session,wall,workarounds,expo,fade,ezoom,scale,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Apr 23 12:04:57 2016 DistUpgraded: 2016-04-22 09:22:44,147 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu EcryptfsInUse: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: COMPAL Electronics Inc Haswell-ULT Integrated Graphics Controller [14c0:0075] InstallationDate: Installed on 2015-01-21 (457 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Compal VAW70 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=8f4bd759-42d2-4828-8470-2aaf6fcb75ff ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to xenial on 2016-04-22 (1 days ago) dmi.bios.date: 07/31/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.01T01 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name1 dmi.board.vendor: Compal dmi.board.version: V1.01T01 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.01T01:bd07/31/2013:svnCompal:pnVAW70:pvrV1.01T01:rvnCompal:rnType2-BoardProductName1:rvrV1.01T01:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: VAW70 dmi.product.version: V1.01T01 dmi.sys.vendor: Compal upstart.unity-panel-service-lockscreen.log: (unity-panel-service:14416): GLib-CRITICAL **: Source ID 4294967295 was not found when attempting to remove it (unity-panel-service:26413): GLib-CRITICAL **: Source ID 4294967295 was not found when attempting to remove it version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version
[Desktop-packages] [Bug 1849416] Re: Xubuntu ping command leading to all of sessions closed
** Package changed: ubuntu => iputils (Ubuntu) ** Tags added: bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to iputils in Ubuntu. https://bugs.launchpad.net/bugs/1849416 Title: Xubuntu ping command leading to all of sessions closed Status in iputils package in Ubuntu: New Bug description: Hi,my server version is Ubuntu 18.04.3 LTS. When I use ping command, all the sessions will be closed and returned socket error 10053. However,it is normal when I ping the valid address likes: ping -c 4 bugs.launchpad.net. But when I ping other address which would return "Destination Host Unreachable", all the distal session in putty or another shell would be colsed with "Connection closed by foreign host". Other commands like netcat have the same error. I checked the syslog without no returned error after using ping for this strange phenomenon, through syslog included some related information: syslog.1:Oct 22 21:15:16 dell systemd-timesyncd[1298]: Synchronized to time server 91.189.89.199:123 (ntp.ubuntu.com). syslog.1:Oct 22 21:17:35 dell systemd-timesyncd[1298]: Timed out waiting for reply from 91.189.89.199:123 (ntp.ubuntu.com). or messages:Oct 22 23:14:53 dell blueman.desktop[3974]: ERROR:dbus.proxies:Introspect error on org.bluez:/: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) messages:Oct 22 23:14:53 dell blueman.desktop[3974]: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) messages:Oct 22 23:14:53 dell blueman.desktop[3974]: ERROR:dbus.proxies:Introspect error on org.bluez:/: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) I guess some daemon programs may peform their function via ping or other ways. User sessions always be closed immediately and connection refusion time usually takes no more than 1 min, and it won't kill running jobs in closed session. Especially, this phenomenon never happens in apt-get and conda or wget command. I have no idea what lead to this strange phenomenon. Please give me advice. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/1849416/+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 1849947] [NEW] Dell XPS 13 (7390) Display Flickering - 19.10
Public bug reported: Hi there, I recently purchased a Dell XPS 13 7390 (Developer Edition). I decided to replace 18.4 LTS with 19.10 and so far it has been pretty smooth. However, there is one issue which occurs frequently whereby the display flickers and becomes unusable. The best way to describe the appearance is that the image becomes heavily distorted. Sometimes it only happens for a split second, other times it is permanently distorted. When this happens, simply closing the laptop lip and re-opening seems to put the display back into it's correct state. I didn't experience this issue on 18.04 LTS which is why I believe it's a Software Bug within 19.10. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Oct 26 11:11:43 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0962] InstallationDate: Installed on 2019-10-25 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. XPS 13 7390 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/23/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.3 dmi.board.name: 0G2D0W dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.3:bd08/23/2019:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0G2D0W:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 dmi.product.sku: 0962 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan 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/1849947 Title: Dell XPS 13 (7390) Display Flickering - 19.10 Status in xorg package in Ubuntu: New Bug description: Hi there, I recently purchased a Dell XPS 13 7390 (Developer Edition). I decided to replace 18.4 LTS with 19.10 and so far it has been pretty smooth. However, there is one issue which occurs frequently whereby the display flickers and becomes unusable. The best way to describe the appearance is that the image becomes heavily distorted. Sometimes it only happens for a split second, other times it is permanently distorted. When this happens, simply closing the laptop lip and re-opening seems to put the display back into it's correct state. I didn't experience this issue on 18.04 LTS which is why I believe it's a Software Bug within 19.10. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Oct 26 11:11:43 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0962] InstallationDate: Installed on 2019-10-25 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. XPS 13 7390 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/23/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.3 dmi.board.name: 0G2D0W dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias:
[Desktop-packages] [Bug 1849416] [NEW] Xubuntu ping command leading to all of sessions closed
You have been subscribed to a public bug: Hi,my server version is Ubuntu 18.04.3 LTS. When I use ping command, all the sessions will be closed and returned socket error 10053. However,it is normal when I ping the valid address likes: ping -c 4 bugs.launchpad.net. But when I ping other address which would return "Destination Host Unreachable", all the distal session in putty or another shell would be colsed with "Connection closed by foreign host". Other commands like netcat have the same error. I checked the syslog without no returned error after using ping for this strange phenomenon, through syslog included some related information: syslog.1:Oct 22 21:15:16 dell systemd-timesyncd[1298]: Synchronized to time server 91.189.89.199:123 (ntp.ubuntu.com). syslog.1:Oct 22 21:17:35 dell systemd-timesyncd[1298]: Timed out waiting for reply from 91.189.89.199:123 (ntp.ubuntu.com). or messages:Oct 22 23:14:53 dell blueman.desktop[3974]: ERROR:dbus.proxies:Introspect error on org.bluez:/: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) messages:Oct 22 23:14:53 dell blueman.desktop[3974]: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) messages:Oct 22 23:14:53 dell blueman.desktop[3974]: ERROR:dbus.proxies:Introspect error on org.bluez:/: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) I guess some daemon programs may peform their function via ping or other ways. User sessions always be closed immediately and connection refusion time usually takes no more than 1 min, and it won't kill running jobs in closed session. Especially, this phenomenon never happens in apt-get and conda or wget command. I have no idea what lead to this strange phenomenon. Please give me advice. Thanks! ** Affects: iputils (Ubuntu) Importance: Undecided Status: New -- Xubuntu ping command leading to all of sessions closed https://bugs.launchpad.net/bugs/1849416 You received this bug notification because you are a member of Desktop Packages, which is subscribed to iputils 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 1753070] Re: Cannot restore default alert sound (Ubuntu bell)
I was facing the same problem And after scavenging through the internet I found a fix Open a terminal And type dconf reset -f / Hope it works for y'all -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1753070 Title: Cannot restore default alert sound (Ubuntu bell) Status in gnome-control-center package in Ubuntu: Confirmed Bug description: After changing the default alert sound in Settings > Sound > Sound Effects, I cannot restore the alert sound to the Ubuntu 17.10 default. Gnome Control Center version: 1:3.26.2-0ubuntu0.2 There are five options in the Sound Effects tab: Default, Bark, Drip, Glass and Sonar. Selecting Default gives the same sound as Drip, which is not the default I had before. I think the sound options come from /usr/share/sounds/gnome/default/alerts where I found Ogg files for the Bark, Drip, Glass and Sonar options (but not for Default). The /usr/share/sounds/ubuntu/stereo/bell.ogg seems to have been the original default alert sound, to which I cannot restore. I am not sure if this is related, but when I opened the Sound Effects tab for the first time, the Alert Volume slider was at 0% and grayed out. The alert sound was working fine, so I guess that default settings from elsewhere were in effect until I started adjusting things in this tab and thereby overriding those default settings. I cannot restore to that grayed out state either in this tab. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.26.2-0ubuntu0.2 ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 3 11:17:54 2018 InstallationDate: Installed on 2018-02-09 (21 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1753070/+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 1849942] Re: 19.10 Gnome Settings and Tweak Tools Window Bar Bug
** Package changed: ubuntu => gnome-control-center (Ubuntu) ** Also affects: gnome-tweak-tool (Ubuntu) Importance: Undecided Status: New ** Tags added: eoan -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1849942 Title: 19.10 Gnome Settings and Tweak Tools Window Bar Bug Status in gnome-control-center package in Ubuntu: New Status in gnome-tweak-tool package in Ubuntu: New Bug description: I upgraded from 19.04 to 19.10 and now there are some strange bugs with the Gnome Settings and the Tweak Tool: https://drive.google.com/file/d/1PpxTRKOqrrPfNLC_0fLSXNZTrsOIWDxg/view?usp=sharing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1849942/+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 1849942] [NEW] 19.10 Gnome Settings and Tweak Tools Window Bar Bug
You have been subscribed to a public bug: I upgraded from 19.04 to 19.10 and now there are some strange bugs with the Gnome Settings and the Tweak Tool: https://drive.google.com/file/d/1PpxTRKOqrrPfNLC_0fLSXNZTrsOIWDxg/view?usp=sharing ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- 19.10 Gnome Settings and Tweak Tools Window Bar Bug https://bugs.launchpad.net/bugs/1849942 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center 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 1849930] Re: Additional VPN Breaks First VPN
** Changed in: gnome-control-center Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1849930 Title: Additional VPN Breaks First VPN Status in gnome-control-center: New Status in NetworkManager: New Status in strongSwan: New Status in gnome-control-center package in Ubuntu: New Bug description: When I add only one L2TP VPN profile to gnome-control-center's Network > VPN settings, it works fine. However, if I add a 2nd L2TP VPN, the 2nd L2TP VPN, not only doesn't work, but it corrupts the first L2TP VPN so that it too stops working. Furthermore, if I remove 2nd L2TP VPN profile (that corrupted the first L2TP VPN) this does NOT repair the corruption to the first L2TP VPN, it remains corrupted. Additionally, removing all VPN profiles and re-adding the first one back, doesn't repair the corruption. Rebooting and adding them back doesn't work either. The only thing that works, that I've found, is completely reinstalling Ubuntu 19.10. Please advise better workarounds than reinstalling. Here's what's in the syslog on a failed VPN Connection attempt: Oct 26 02:58:35 workstation5 NetworkManager[1241]: [1572076715.5632] audit: op="connection-activate" uuid="1942cf95-93b1-4e74-a44a-947a46bffb5a" name="L2TP VPN1" pid=3531 uid=1000 result="success" Oct 26 02:58:35 workstation5 NetworkManager[1241]: [1572076715.5702] vpn-connection[0x5642f421c750,1932cf95-91b1-4e85-a44a-498a56befb5a,"L2TP VPN1",0]: Started the VPN service, PID 7273 Oct 26 02:58:35 workstation5 NetworkManager[1241]: [1572076715.5747] vpn-connection[0x5642f421c750,1932cf95-91b1-4e85-a44a-498a56befb5a,"L2TP VPN1",0]: Saw the service appear; activating connection Oct 26 02:58:35 workstation5 NetworkManager[1241]: [1572076715.6566] vpn-connection[0x5642f421c750,1932cf95-91b1-4e85-a44a-498a56befb5a,"L2TP VPN1",0]: VPN connection: (ConnectInteractive) reply received Oct 26 02:58:35 workstation5 NetworkManager[1241]: Stopping strongSwan IPsec failed: starter is not running Oct 26 02:58:37 workstation5 NetworkManager[1241]: Starting strongSwan 5.7.2 IPsec [starter]... Oct 26 02:58:37 workstation5 NetworkManager[1241]: Loading config setup Oct 26 02:58:37 workstation5 NetworkManager[1241]: Loading conn '1942cf95-93b1-4e74-a44a-947a46bffb5a' Oct 26 02:58:37 workstation5 NetworkManager[1241]: found netkey IPsec stack Oct 26 02:58:48 workstation5 NetworkManager[1241]: Stopping strongSwan IPsec... Oct 26 02:58:48 workstation5 NetworkManager[1241]: initiating Main Mode IKE_SA 1942cf95-93b1-4e74-a44a-947a46bffb5a[1] to 49.230.24.121 Oct 26 02:58:48 workstation5 NetworkManager[1241]: generating ID_PROT request 0 [ SA V V V V V ] Oct 26 02:58:48 workstation5 NetworkManager[1241]: sending packet: from 192.168.1.2[500] to 49.230.24.121[500] (236 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: received packet: from 49.230.24.121[500] to 192.168.1.2[500] (156 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: parsed ID_PROT response 0 [ SA V V V V ] Oct 26 02:58:48 workstation5 NetworkManager[1241]: received XAuth vendor ID Oct 26 02:58:48 workstation5 NetworkManager[1241]: received DPD vendor ID Oct 26 02:58:48 workstation5 NetworkManager[1241]: received FRAGMENTATION vendor ID Oct 26 02:58:48 workstation5 NetworkManager[1241]: received NAT-T (RFC 3947) vendor ID Oct 26 02:58:48 workstation5 NetworkManager[1241]: selected proposal: IKE:3DES_CBC/HMAC_SHA1_96/PRF_HMAC_SHA1/MODP_1024 Oct 26 02:58:48 workstation5 NetworkManager[1241]: generating ID_PROT request 0 [ KE No NAT-D NAT-D ] Oct 26 02:58:48 workstation5 NetworkManager[1241]: sending packet: from 192.168.1.2[500] to 49.230.24.121[500] (244 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: received packet: from 49.230.24.121[500] to 192.168.1.2[500] (244 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: parsed ID_PROT response 0 [ KE No NAT-D NAT-D ] Oct 26 02:58:48 workstation5 NetworkManager[1241]: local host is behind NAT, sending keep alives Oct 26 02:58:48 workstation5 NetworkManager[1241]: generating ID_PROT request 0 [ ID HASH ] Oct 26 02:58:48 workstation5 NetworkManager[1241]: sending packet: from 192.168.1.2[4500] to 49.230.24.121[4500] (68 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: received packet: from 49.230.24.121[500] to 192.168.1.2[500] (68 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: invalid HASH_V1 payload length, decryption failed? Oct 26 02:58:48 workstation5 NetworkManager[1241]: could not decrypt payloads Oct 26 02:58:48 workstation5 NetworkManager[1241]: message parsing failed Oct 26 02:58:48 workstation5 NetworkManager[1241]: ignore malformed INFORMATIONAL request Oct 26 02:58:48 workstation5 NetworkManager[1241]: INFORMATIONAL_V1 request
[Desktop-packages] [Bug 1849930] Re: Additional VPN Breaks First VPN
** Also affects: strongswan Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1849930 Title: Additional VPN Breaks First VPN Status in gnome-control-center: New Status in NetworkManager: New Status in strongSwan: New Status in gnome-control-center package in Ubuntu: New Bug description: When I add only one L2TP VPN profile to gnome-control-center's Network > VPN settings, it works fine. However, if I add a 2nd L2TP VPN, the 2nd L2TP VPN, not only doesn't work, but it corrupts the first L2TP VPN so that it too stops working. Furthermore, if I remove 2nd L2TP VPN profile (that corrupted the first L2TP VPN) this does NOT repair the corruption to the first L2TP VPN, it remains corrupted. Additionally, removing all VPN profiles and re-adding the first one back, doesn't repair the corruption. Rebooting and adding them back doesn't work either. The only thing that works, that I've found, is completely reinstalling Ubuntu 19.10. Please advise better workarounds than reinstalling. Here's what's in the syslog on a failed VPN Connection attempt: Oct 26 02:58:35 workstation5 NetworkManager[1241]: [1572076715.5632] audit: op="connection-activate" uuid="1942cf95-93b1-4e74-a44a-947a46bffb5a" name="L2TP VPN1" pid=3531 uid=1000 result="success" Oct 26 02:58:35 workstation5 NetworkManager[1241]: [1572076715.5702] vpn-connection[0x5642f421c750,1932cf95-91b1-4e85-a44a-498a56befb5a,"L2TP VPN1",0]: Started the VPN service, PID 7273 Oct 26 02:58:35 workstation5 NetworkManager[1241]: [1572076715.5747] vpn-connection[0x5642f421c750,1932cf95-91b1-4e85-a44a-498a56befb5a,"L2TP VPN1",0]: Saw the service appear; activating connection Oct 26 02:58:35 workstation5 NetworkManager[1241]: [1572076715.6566] vpn-connection[0x5642f421c750,1932cf95-91b1-4e85-a44a-498a56befb5a,"L2TP VPN1",0]: VPN connection: (ConnectInteractive) reply received Oct 26 02:58:35 workstation5 NetworkManager[1241]: Stopping strongSwan IPsec failed: starter is not running Oct 26 02:58:37 workstation5 NetworkManager[1241]: Starting strongSwan 5.7.2 IPsec [starter]... Oct 26 02:58:37 workstation5 NetworkManager[1241]: Loading config setup Oct 26 02:58:37 workstation5 NetworkManager[1241]: Loading conn '1942cf95-93b1-4e74-a44a-947a46bffb5a' Oct 26 02:58:37 workstation5 NetworkManager[1241]: found netkey IPsec stack Oct 26 02:58:48 workstation5 NetworkManager[1241]: Stopping strongSwan IPsec... Oct 26 02:58:48 workstation5 NetworkManager[1241]: initiating Main Mode IKE_SA 1942cf95-93b1-4e74-a44a-947a46bffb5a[1] to 49.230.24.121 Oct 26 02:58:48 workstation5 NetworkManager[1241]: generating ID_PROT request 0 [ SA V V V V V ] Oct 26 02:58:48 workstation5 NetworkManager[1241]: sending packet: from 192.168.1.2[500] to 49.230.24.121[500] (236 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: received packet: from 49.230.24.121[500] to 192.168.1.2[500] (156 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: parsed ID_PROT response 0 [ SA V V V V ] Oct 26 02:58:48 workstation5 NetworkManager[1241]: received XAuth vendor ID Oct 26 02:58:48 workstation5 NetworkManager[1241]: received DPD vendor ID Oct 26 02:58:48 workstation5 NetworkManager[1241]: received FRAGMENTATION vendor ID Oct 26 02:58:48 workstation5 NetworkManager[1241]: received NAT-T (RFC 3947) vendor ID Oct 26 02:58:48 workstation5 NetworkManager[1241]: selected proposal: IKE:3DES_CBC/HMAC_SHA1_96/PRF_HMAC_SHA1/MODP_1024 Oct 26 02:58:48 workstation5 NetworkManager[1241]: generating ID_PROT request 0 [ KE No NAT-D NAT-D ] Oct 26 02:58:48 workstation5 NetworkManager[1241]: sending packet: from 192.168.1.2[500] to 49.230.24.121[500] (244 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: received packet: from 49.230.24.121[500] to 192.168.1.2[500] (244 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: parsed ID_PROT response 0 [ KE No NAT-D NAT-D ] Oct 26 02:58:48 workstation5 NetworkManager[1241]: local host is behind NAT, sending keep alives Oct 26 02:58:48 workstation5 NetworkManager[1241]: generating ID_PROT request 0 [ ID HASH ] Oct 26 02:58:48 workstation5 NetworkManager[1241]: sending packet: from 192.168.1.2[4500] to 49.230.24.121[4500] (68 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: received packet: from 49.230.24.121[500] to 192.168.1.2[500] (68 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: invalid HASH_V1 payload length, decryption failed? Oct 26 02:58:48 workstation5 NetworkManager[1241]: could not decrypt payloads Oct 26 02:58:48 workstation5 NetworkManager[1241]: message parsing failed Oct 26 02:58:48 workstation5 NetworkManager[1241]: ignore malformed INFORMATIONAL request Oct 26 02:58:48 workstation5 NetworkManager[1241]: INFORMATIONAL_V1 req
[Desktop-packages] [Bug 1849907] Re: Add Online Account Nextcloud no Apply button
Thanks for moving the bug to the correct section. When creating it I hade to choices "Ubunto-docs" or "I don't know". I selected the latter. Looking at the reviews of "Online account" it looks that I am not alone. Someone else reported the problem. But I think I have an idea. The Ubuntu installation is a stock installation, but I think I have changed how menues and/or title bar of window should show. I will look into that. Regardless, it is not a good implementation if submit buttons disapear if you change system settings of windows. The function of a window should remain, even if the theam of the desktop change. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1849907 Title: Add Online Account Nextcloud no Apply button Status in gnome-online-accounts package in Ubuntu: Incomplete Bug description: I am trying to add an online account, nextcloud three fields show, server, username and password. There is no Apply or OK button. I cannot add the account. Resizing the window does not help. Fields just get longer, still no buttons. Ubuntu 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1849907/+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 1074779] Re: llvmpipe used after clean install instead of intel
I have Ubuntu 18.04.3 clean install and Sandybridge. Sometime everything normal and boot Sandybridge Mobile GPU. But sometime boot LLVMPIPE. Log out and log in fix the problem. Just the known. What should ı do? Create file? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1074779 Title: llvmpipe used after clean install instead of intel Status in Linux Mint: Fix Released Status in xserver-xorg-video-intel package in Ubuntu: Invalid Bug description: After installing ubuntu 12.10 llvmpipe is loaded instead of intel graphics driver, before in ubuntu 12.04 it was working very well with the intel drivers out of the box. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7 Uname: Linux 3.5.0-18-generic x86_64 ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sat Nov 3 23:53:55 2012 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 07) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Device [1558:5140] NVIDIA Corporation GF108 [GeForce GT 540M] [10de:0df4] (rev a1) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Device [1558:5140] InstallationDate: Installed on 2012-11-03 (0 days ago) InstallationMedia: Ubuntu GNOME Remix 12.10 "Quantal Quetzal" - Release amd64(20121018) MachineType: CLEVO CO. W150HNM/W170HN MarkForUpload: True ProcEnviron: LANGUAGE=pt:pt_BR:en TERM=xterm PATH=(custom, no user) LANG=pt_PT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-18-generic root=UUID=9f0065ef-dbaf-4c00-92a1-f4397031fb22 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/07/2011 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: HR_2.1.0.128 X64 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: W150HNM/W170HN dmi.board.vendor: CLEVO CO. dmi.board.version: D03 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: CLEVO CO. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrHR_2.1.0.128X64:bd10/07/2011:svnCLEVOCO.:pnW150HNM/W170HN:pvr0.1:rvnCLEVOCO.:rnW150HNM/W170HN:rvrD03:cvnCLEVOCO.:ct9:cvr0.1: dmi.product.name: W150HNM/W170HN dmi.product.version: 0.1 dmi.sys.vendor: CLEVO CO. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.39-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120913.8637f772-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1074779/+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 1849693] Re: [snap] Upgrading from kubuntu 19.04 to 19.10 lost all chromium settings
Occurrences if chromium in the dpkg.log: root@flupp:/var/log# grep chromium dpkg.log 2019-10-24 16:15:45 upgrade chromium-browser-l10n:all 76.0.3809.100-0ubuntu0.19.04.1 77.0.3865.120-0ubuntu1~snap1 2019-10-24 16:15:45 status half-configured chromium-browser-l10n:all 76.0.3809.100-0ubuntu0.19.04.1 2019-10-24 16:15:45 status unpacked chromium-browser-l10n:all 76.0.3809.100-0ubuntu0.19.04.1 2019-10-24 16:15:45 status half-installed chromium-browser-l10n:all 76.0.3809.100-0ubuntu0.19.04.1 2019-10-24 16:15:45 status unpacked chromium-browser-l10n:all 77.0.3865.120-0ubuntu1~snap1 2019-10-24 16:15:45 upgrade chromium-browser:amd64 76.0.3809.100-0ubuntu0.19.04.1 77.0.3865.120-0ubuntu1~snap1 2019-10-24 16:15:45 status half-configured chromium-browser:amd64 76.0.3809.100-0ubuntu0.19.04.1 2019-10-24 16:15:45 status unpacked chromium-browser:amd64 76.0.3809.100-0ubuntu0.19.04.1 2019-10-24 16:15:46 status half-installed chromium-browser:amd64 76.0.3809.100-0ubuntu0.19.04.1 2019-10-24 16:17:26 status unpacked chromium-browser:amd64 77.0.3865.120-0ubuntu1~snap1 2019-10-24 16:18:43 upgrade chromium-codecs-ffmpeg-extra:amd64 76.0.3809.100-0ubuntu0.19.04.1 77.0.3865.120-0ubuntu1~snap1 2019-10-24 16:18:43 status half-configured chromium-codecs-ffmpeg-extra:amd64 76.0.3809.100-0ubuntu0.19.04.1 2019-10-24 16:18:43 status unpacked chromium-codecs-ffmpeg-extra:amd64 76.0.3809.100-0ubuntu0.19.04.1 2019-10-24 16:18:43 status half-installed chromium-codecs-ffmpeg-extra:amd64 76.0.3809.100-0ubuntu0.19.04.1 2019-10-24 16:18:43 status unpacked chromium-codecs-ffmpeg-extra:amd64 77.0.3865.120-0ubuntu1~snap1 2019-10-24 16:22:23 configure chromium-codecs-ffmpeg-extra:amd64 77.0.3865.120-0ubuntu1~snap1 2019-10-24 16:22:23 status unpacked chromium-codecs-ffmpeg-extra:amd64 77.0.3865.120-0ubuntu1~snap1 2019-10-24 16:22:23 status half-configured chromium-codecs-ffmpeg-extra:amd64 77.0.3865.120-0ubuntu1~snap1 2019-10-24 16:22:23 status installed chromium-codecs-ffmpeg-extra:amd64 77.0.3865.120-0ubuntu1~snap1 2019-10-24 16:44:26 configure chromium-browser:amd64 77.0.3865.120-0ubuntu1~snap1 2019-10-24 16:44:26 status unpacked chromium-browser:amd64 77.0.3865.120-0ubuntu1~snap1 2019-10-24 16:44:26 status half-configured chromium-browser:amd64 77.0.3865.120-0ubuntu1~snap1 2019-10-24 16:44:26 status installed chromium-browser:amd64 77.0.3865.120-0ubuntu1~snap1 2019-10-24 16:44:26 configure chromium-browser-l10n:all 77.0.3865.120-0ubuntu1~snap1 2019-10-24 16:44:26 status unpacked chromium-browser-l10n:all 77.0.3865.120-0ubuntu1~snap1 2019-10-24 16:44:26 status half-configured chromium-browser-l10n:all 77.0.3865.120-0ubuntu1~snap1 2019-10-24 16:44:26 status installed chromium-browser-l10n:all 77.0.3865.120-0ubuntu1~snap1 2019-10-24 16:47:12 status installed chromium-browser-l10n:all 77.0.3865.120-0ubuntu1~snap1 2019-10-24 16:47:13 remove chromium-browser-l10n:all 77.0.3865.120-0ubuntu1~snap1 2019-10-24 16:47:13 status half-configured chromium-browser-l10n:all 77.0.3865.120-0ubuntu1~snap1 2019-10-24 16:47:13 status half-installed chromium-browser-l10n:all 77.0.3865.120-0ubuntu1~snap1 2019-10-24 16:47:13 status config-files chromium-browser-l10n:all 77.0.3865.120-0ubuntu1~snap1 2019-10-24 16:47:13 status not-installed chromium-browser-l10n:all After starting the PC and logging into KDE without starting chromium: gert@flupp:~$ snap connections chromium | grep password password-manager-service chromium:password-manager-service :password-manager-service manual I remember that after the upgrade when the configs have not been transfered, that last "manual" was not printed. I think it was a "-" instead. After starting up the connection manually as mentioned in the bug 1849160 the "manual" was printed. After removing the ~/snap/chromium/current/.config/ directory and starting chromium the following was printed to konsole. (And the settings were not transfered.) gert@flupp:~$ which chromium /snap/bin/chromium gert@flupp:~$ chromium [4498:4498:1026/104128.629497:ERROR:sandbox_linux.cc(369)] InitializeSandbox() called with multiple threads in process gpu-process. [4498:4498:1026/104128.968059:ERROR:buffer_manager.cc(488)] [.DisplayCompositor]GL ERROR :GL_INVALID_OPERATION : glBufferData: <- error from previous GL command [4560:1:1026/104130.143320:ERROR:child_process_sandbox_support_impl_linux.cc(81)] FontService unique font name matching request did not receive a response. [4560:1:1026/104130.143846:ERROR:child_process_sandbox_support_impl_linux.cc(81)] FontService unique font name matching request did not receive a response. [4573:1:1026/104132.869494:ERROR:child_process_sandbox_support_impl_linux.cc(81)] FontService unique font name matching request did not receive a response. [4573:1:1026/104132.869978:ERROR:child_process_sandbox_support_impl_linux.cc(81)] FontService unique font name matching request did not receive a response. If I can test and report something else, please let me know. -- You
[Desktop-packages] [Bug 1849931] Re: nautilus crashed with SIGSEGV
*** This bug is a duplicate of bug 1844026 *** https://bugs.launchpad.net/bugs/1844026 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1844026, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1849931/+attachment/5300256/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1849931/+attachment/5300258/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1849931/+attachment/5300262/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1849931/+attachment/5300263/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1849931/+attachment/5300264/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1849931/+attachment/5300265/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1849931/+attachment/5300266/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1844026 nautilus crashed with SIGSEGV ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1849931 Title: nautilus crashed with SIGSEGV Status in nautilus package in Ubuntu: New Bug description: Unknown crash ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: nautilus 1:3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Oct 26 13:53:17 2019 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'234' b'org.gnome.nautilus.window-state' b'initial-size' b'(1376, 742)' b'org.gnome.nautilus.preferences' b'show-create-link' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']" InstallationDate: Installed on 2019-06-23 (124 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcCmdline: /usr/bin/nautilus --gapplication-service SegvAnalysis: Segfault happened at: 0x7fe5af3ee982:mov0x380(%rax),%rax PC (0x7fe5af3ee982) ok source "0x380(%rax)" (0x0380) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: nautilus StacktraceTop: () at /lib/x86_64-linux-gnu/libgtk-3.so.0 () at /lib/x86_64-linux-gnu/libgtk-3.so.0 () at /lib/x86_64-linux-gnu/libgtk-3.so.0 () at /lib/x86_64-linux-gnu/libgtk-3.so.0 () at /lib/x86_64-linux-gnu/libgtk-3.so.0 Title: nautilus crashed with SIGSEGV UpgradeStatus: Upgraded to eoan on 2019-10-24 (1 days ago) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo wireshark modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2019-06-29T23:49:14.971566 separator: usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1849931/+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 1849930] Re: Additional VPN Breaks First VPN
** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/issues #746 https://gitlab.gnome.org/GNOME/gnome-control-center/issues/746 ** Also affects: gnome-control-center via https://gitlab.gnome.org/GNOME/gnome-control-center/issues/746 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1849930 Title: Additional VPN Breaks First VPN Status in gnome-control-center: Unknown Status in NetworkManager: New Status in gnome-control-center package in Ubuntu: New Bug description: When I add only one L2TP VPN profile to gnome-control-center's Network > VPN settings, it works fine. However, if I add a 2nd L2TP VPN, the 2nd L2TP VPN, not only doesn't work, but it corrupts the first L2TP VPN so that it too stops working. Furthermore, if I remove 2nd L2TP VPN profile (that corrupted the first L2TP VPN) this does NOT repair the corruption to the first L2TP VPN, it remains corrupted. Additionally, removing all VPN profiles and re-adding the first one back, doesn't repair the corruption. Rebooting and adding them back doesn't work either. The only thing that works, that I've found, is completely reinstalling Ubuntu 19.10. Please advise better workarounds than reinstalling. Here's what's in the syslog on a failed VPN Connection attempt: Oct 26 02:58:35 workstation5 NetworkManager[1241]: [1572076715.5632] audit: op="connection-activate" uuid="1942cf95-93b1-4e74-a44a-947a46bffb5a" name="L2TP VPN1" pid=3531 uid=1000 result="success" Oct 26 02:58:35 workstation5 NetworkManager[1241]: [1572076715.5702] vpn-connection[0x5642f421c750,1932cf95-91b1-4e85-a44a-498a56befb5a,"L2TP VPN1",0]: Started the VPN service, PID 7273 Oct 26 02:58:35 workstation5 NetworkManager[1241]: [1572076715.5747] vpn-connection[0x5642f421c750,1932cf95-91b1-4e85-a44a-498a56befb5a,"L2TP VPN1",0]: Saw the service appear; activating connection Oct 26 02:58:35 workstation5 NetworkManager[1241]: [1572076715.6566] vpn-connection[0x5642f421c750,1932cf95-91b1-4e85-a44a-498a56befb5a,"L2TP VPN1",0]: VPN connection: (ConnectInteractive) reply received Oct 26 02:58:35 workstation5 NetworkManager[1241]: Stopping strongSwan IPsec failed: starter is not running Oct 26 02:58:37 workstation5 NetworkManager[1241]: Starting strongSwan 5.7.2 IPsec [starter]... Oct 26 02:58:37 workstation5 NetworkManager[1241]: Loading config setup Oct 26 02:58:37 workstation5 NetworkManager[1241]: Loading conn '1942cf95-93b1-4e74-a44a-947a46bffb5a' Oct 26 02:58:37 workstation5 NetworkManager[1241]: found netkey IPsec stack Oct 26 02:58:48 workstation5 NetworkManager[1241]: Stopping strongSwan IPsec... Oct 26 02:58:48 workstation5 NetworkManager[1241]: initiating Main Mode IKE_SA 1942cf95-93b1-4e74-a44a-947a46bffb5a[1] to 49.230.24.121 Oct 26 02:58:48 workstation5 NetworkManager[1241]: generating ID_PROT request 0 [ SA V V V V V ] Oct 26 02:58:48 workstation5 NetworkManager[1241]: sending packet: from 192.168.1.2[500] to 49.230.24.121[500] (236 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: received packet: from 49.230.24.121[500] to 192.168.1.2[500] (156 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: parsed ID_PROT response 0 [ SA V V V V ] Oct 26 02:58:48 workstation5 NetworkManager[1241]: received XAuth vendor ID Oct 26 02:58:48 workstation5 NetworkManager[1241]: received DPD vendor ID Oct 26 02:58:48 workstation5 NetworkManager[1241]: received FRAGMENTATION vendor ID Oct 26 02:58:48 workstation5 NetworkManager[1241]: received NAT-T (RFC 3947) vendor ID Oct 26 02:58:48 workstation5 NetworkManager[1241]: selected proposal: IKE:3DES_CBC/HMAC_SHA1_96/PRF_HMAC_SHA1/MODP_1024 Oct 26 02:58:48 workstation5 NetworkManager[1241]: generating ID_PROT request 0 [ KE No NAT-D NAT-D ] Oct 26 02:58:48 workstation5 NetworkManager[1241]: sending packet: from 192.168.1.2[500] to 49.230.24.121[500] (244 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: received packet: from 49.230.24.121[500] to 192.168.1.2[500] (244 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: parsed ID_PROT response 0 [ KE No NAT-D NAT-D ] Oct 26 02:58:48 workstation5 NetworkManager[1241]: local host is behind NAT, sending keep alives Oct 26 02:58:48 workstation5 NetworkManager[1241]: generating ID_PROT request 0 [ ID HASH ] Oct 26 02:58:48 workstation5 NetworkManager[1241]: sending packet: from 192.168.1.2[4500] to 49.230.24.121[4500] (68 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: received packet: from 49.230.24.121[500] to 192.168.1.2[500] (68 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: invalid HASH_V1 payload length, decryption failed? Oct 26 02:58:48 workstation5 NetworkManager[1241]: could not decrypt payloads Oct 26 02:58:48 workstation5 NetworkMan
[Desktop-packages] [Bug 1849930] [NEW] Additional VPN Breaks First VPN
Public bug reported: When I add only one L2TP VPN profile to gnome-control-center's Network > VPN settings, it works fine. However, if I add a 2nd L2TP VPN, the 2nd L2TP VPN, not only doesn't work, but it corrupts the first L2TP VPN so that it too stops working. Furthermore, if I remove 2nd L2TP VPN profile (that corrupted the first L2TP VPN) this does NOT repair the corruption to the first L2TP VPN, it remains corrupted. Additionally, removing all VPN profiles and re-adding the first one back, doesn't repair the corruption. Rebooting and adding them back doesn't work either. The only thing that works, that I've found, is completely reinstalling Ubuntu 19.10. Please advise better workarounds than reinstalling. Here's what's in the syslog on a failed VPN Connection attempt: Oct 26 02:58:35 workstation5 NetworkManager[1241]: [1572076715.5632] audit: op="connection-activate" uuid="1942cf95-93b1-4e74-a44a-947a46bffb5a" name="L2TP VPN1" pid=3531 uid=1000 result="success" Oct 26 02:58:35 workstation5 NetworkManager[1241]: [1572076715.5702] vpn-connection[0x5642f421c750,1932cf95-91b1-4e85-a44a-498a56befb5a,"L2TP VPN1",0]: Started the VPN service, PID 7273 Oct 26 02:58:35 workstation5 NetworkManager[1241]: [1572076715.5747] vpn-connection[0x5642f421c750,1932cf95-91b1-4e85-a44a-498a56befb5a,"L2TP VPN1",0]: Saw the service appear; activating connection Oct 26 02:58:35 workstation5 NetworkManager[1241]: [1572076715.6566] vpn-connection[0x5642f421c750,1932cf95-91b1-4e85-a44a-498a56befb5a,"L2TP VPN1",0]: VPN connection: (ConnectInteractive) reply received Oct 26 02:58:35 workstation5 NetworkManager[1241]: Stopping strongSwan IPsec failed: starter is not running Oct 26 02:58:37 workstation5 NetworkManager[1241]: Starting strongSwan 5.7.2 IPsec [starter]... Oct 26 02:58:37 workstation5 NetworkManager[1241]: Loading config setup Oct 26 02:58:37 workstation5 NetworkManager[1241]: Loading conn '1942cf95-93b1-4e74-a44a-947a46bffb5a' Oct 26 02:58:37 workstation5 NetworkManager[1241]: found netkey IPsec stack Oct 26 02:58:48 workstation5 NetworkManager[1241]: Stopping strongSwan IPsec... Oct 26 02:58:48 workstation5 NetworkManager[1241]: initiating Main Mode IKE_SA 1942cf95-93b1-4e74-a44a-947a46bffb5a[1] to 49.230.24.121 Oct 26 02:58:48 workstation5 NetworkManager[1241]: generating ID_PROT request 0 [ SA V V V V V ] Oct 26 02:58:48 workstation5 NetworkManager[1241]: sending packet: from 192.168.1.2[500] to 49.230.24.121[500] (236 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: received packet: from 49.230.24.121[500] to 192.168.1.2[500] (156 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: parsed ID_PROT response 0 [ SA V V V V ] Oct 26 02:58:48 workstation5 NetworkManager[1241]: received XAuth vendor ID Oct 26 02:58:48 workstation5 NetworkManager[1241]: received DPD vendor ID Oct 26 02:58:48 workstation5 NetworkManager[1241]: received FRAGMENTATION vendor ID Oct 26 02:58:48 workstation5 NetworkManager[1241]: received NAT-T (RFC 3947) vendor ID Oct 26 02:58:48 workstation5 NetworkManager[1241]: selected proposal: IKE:3DES_CBC/HMAC_SHA1_96/PRF_HMAC_SHA1/MODP_1024 Oct 26 02:58:48 workstation5 NetworkManager[1241]: generating ID_PROT request 0 [ KE No NAT-D NAT-D ] Oct 26 02:58:48 workstation5 NetworkManager[1241]: sending packet: from 192.168.1.2[500] to 49.230.24.121[500] (244 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: received packet: from 49.230.24.121[500] to 192.168.1.2[500] (244 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: parsed ID_PROT response 0 [ KE No NAT-D NAT-D ] Oct 26 02:58:48 workstation5 NetworkManager[1241]: local host is behind NAT, sending keep alives Oct 26 02:58:48 workstation5 NetworkManager[1241]: generating ID_PROT request 0 [ ID HASH ] Oct 26 02:58:48 workstation5 NetworkManager[1241]: sending packet: from 192.168.1.2[4500] to 49.230.24.121[4500] (68 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: received packet: from 49.230.24.121[500] to 192.168.1.2[500] (68 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: invalid HASH_V1 payload length, decryption failed? Oct 26 02:58:48 workstation5 NetworkManager[1241]: could not decrypt payloads Oct 26 02:58:48 workstation5 NetworkManager[1241]: message parsing failed Oct 26 02:58:48 workstation5 NetworkManager[1241]: ignore malformed INFORMATIONAL request Oct 26 02:58:48 workstation5 NetworkManager[1241]: INFORMATIONAL_V1 request with message ID 3016741680 processing failed Oct 26 02:58:48 workstation5 NetworkManager[1241]: sending retransmit 1 of request message ID 0, seq 3 Oct 26 02:58:48 workstation5 NetworkManager[1241]: sending packet: from 192.168.1.2[4500] to 49.230.24.121[4500] (68 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: received packet: from 49.230.24.121[500] to 192.168.1.2[500] (68 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: invalid HASH_V1 payload length, decryption failed? Oct 26 02:58:48 workstation5 Net
[Desktop-packages] [Bug 1849930] Re: Additional VPN Breaks First VPN
I've attached the syslog for easier viewing. ** Attachment added: "syslog.txt" https://bugs.launchpad.net/network-manager/+bug/1849930/+attachment/5300267/+files/syslog.txt ** Description changed: When I add only one L2TP VPN profile to gnome-control-center's Network > - VPN setting, it works fine. + VPN settings, it works fine. However, if I add a 2nd L2TP VPN, the 2nd L2TP VPN, not only doesn't work, but it corrupts the first L2TP VPN so that it too stops working. Furthermore, if I remove 2nd L2TP VPN profile (that corrupted the first L2TP VPN) this does NOT repair the corruption to the first L2TP VPN, it remains corrupted. Additionally, removing all VPN profiles and re-adding the first one back, doesn't repair the corruption. Rebooting and adding them back doesn't work either. The only thing that works, that I've found, is completely reinstalling Ubuntu 19.10. Please advise better workarounds than reinstalling. Here's what's in the syslog on a failed VPN Connection attempt: Oct 26 02:58:35 workstation5 NetworkManager[1241]: [1572076715.5632] audit: op="connection-activate" uuid="1942cf95-93b1-4e74-a44a-947a46bffb5a" name="L2TP VPN1" pid=3531 uid=1000 result="success" Oct 26 02:58:35 workstation5 NetworkManager[1241]: [1572076715.5702] vpn-connection[0x5642f421c750,1932cf95-91b1-4e85-a44a-498a56befb5a,"L2TP VPN1",0]: Started the VPN service, PID 7273 Oct 26 02:58:35 workstation5 NetworkManager[1241]: [1572076715.5747] vpn-connection[0x5642f421c750,1932cf95-91b1-4e85-a44a-498a56befb5a,"L2TP VPN1",0]: Saw the service appear; activating connection Oct 26 02:58:35 workstation5 NetworkManager[1241]: [1572076715.6566] vpn-connection[0x5642f421c750,1932cf95-91b1-4e85-a44a-498a56befb5a,"L2TP VPN1",0]: VPN connection: (ConnectInteractive) reply received Oct 26 02:58:35 workstation5 NetworkManager[1241]: Stopping strongSwan IPsec failed: starter is not running Oct 26 02:58:37 workstation5 NetworkManager[1241]: Starting strongSwan 5.7.2 IPsec [starter]... Oct 26 02:58:37 workstation5 NetworkManager[1241]: Loading config setup Oct 26 02:58:37 workstation5 NetworkManager[1241]: Loading conn '1942cf95-93b1-4e74-a44a-947a46bffb5a' Oct 26 02:58:37 workstation5 NetworkManager[1241]: found netkey IPsec stack Oct 26 02:58:48 workstation5 NetworkManager[1241]: Stopping strongSwan IPsec... Oct 26 02:58:48 workstation5 NetworkManager[1241]: initiating Main Mode IKE_SA 1942cf95-93b1-4e74-a44a-947a46bffb5a[1] to 49.230.24.121 Oct 26 02:58:48 workstation5 NetworkManager[1241]: generating ID_PROT request 0 [ SA V V V V V ] Oct 26 02:58:48 workstation5 NetworkManager[1241]: sending packet: from 192.168.1.2[500] to 49.230.24.121[500] (236 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: received packet: from 49.230.24.121[500] to 192.168.1.2[500] (156 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: parsed ID_PROT response 0 [ SA V V V V ] Oct 26 02:58:48 workstation5 NetworkManager[1241]: received XAuth vendor ID Oct 26 02:58:48 workstation5 NetworkManager[1241]: received DPD vendor ID Oct 26 02:58:48 workstation5 NetworkManager[1241]: received FRAGMENTATION vendor ID Oct 26 02:58:48 workstation5 NetworkManager[1241]: received NAT-T (RFC 3947) vendor ID Oct 26 02:58:48 workstation5 NetworkManager[1241]: selected proposal: IKE:3DES_CBC/HMAC_SHA1_96/PRF_HMAC_SHA1/MODP_1024 Oct 26 02:58:48 workstation5 NetworkManager[1241]: generating ID_PROT request 0 [ KE No NAT-D NAT-D ] Oct 26 02:58:48 workstation5 NetworkManager[1241]: sending packet: from 192.168.1.2[500] to 49.230.24.121[500] (244 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: received packet: from 49.230.24.121[500] to 192.168.1.2[500] (244 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: parsed ID_PROT response 0 [ KE No NAT-D NAT-D ] Oct 26 02:58:48 workstation5 NetworkManager[1241]: local host is behind NAT, sending keep alives Oct 26 02:58:48 workstation5 NetworkManager[1241]: generating ID_PROT request 0 [ ID HASH ] Oct 26 02:58:48 workstation5 NetworkManager[1241]: sending packet: from 192.168.1.2[4500] to 49.230.24.121[4500] (68 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: received packet: from 49.230.24.121[500] to 192.168.1.2[500] (68 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: invalid HASH_V1 payload length, decryption failed? Oct 26 02:58:48 workstation5 NetworkManager[1241]: could not decrypt payloads Oct 26 02:58:48 workstation5 NetworkManager[1241]: message parsing failed Oct 26 02:58:48 workstation5 NetworkManager[1241]: ignore malformed INFORMATIONAL request Oct 26 02:58:48 workstation5 NetworkManager[1241]: INFORMATIONAL_V1 request with message ID 3016741680 processing failed Oct 26 02:58:48 workstation5 NetworkManager[1241]: sending retransmit 1 of request message ID 0, seq 3 Oct 26 02:58:48 workstation5 NetworkManager[1241]: sending pack
[Desktop-packages] [Bug 1849928] Re: Dock stays ontop of Xscreensaver
Also reported at: https://github.com/micheleg/dash-to-dock/issues/1002 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1849928 Title: Dock stays ontop of Xscreensaver Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: Ubuntu 20.04 development version with kernel 5.3.0-18-generic up to date to latest @ 26/10/2019 The dock stays visible after Xscreensaver becomes active the screensaver flows under down the dock (see attachment) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-ubuntu-dock 67ubuntu19.10.1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 26 09:12:44 2019 InstallationDate: Installed on 2019-10-25 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191021) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1849928/+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 1849928] [NEW] Dock stays ontop of Xscreensaver
Public bug reported: Ubuntu 20.04 development version with kernel 5.3.0-18-generic up to date to latest @ 26/10/2019 The dock stays visible after Xscreensaver becomes active the screensaver flows under down the dock (see attachment) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-ubuntu-dock 67ubuntu19.10.1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 26 09:12:44 2019 InstallationDate: Installed on 2019-10-25 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191021) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1849928 Title: Dock stays ontop of Xscreensaver Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: Ubuntu 20.04 development version with kernel 5.3.0-18-generic up to date to latest @ 26/10/2019 The dock stays visible after Xscreensaver becomes active the screensaver flows under down the dock (see attachment) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-ubuntu-dock 67ubuntu19.10.1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 26 09:12:44 2019 InstallationDate: Installed on 2019-10-25 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191021) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1849928/+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 1849928] Re: Dock stays ontop of Xscreensaver
Dock and Xscreensaver ** Attachment added: "Dock and screensaver" https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1849928/+attachment/5300252/+files/image20191025_171918739.jpg ** Bug watch added: github.com/micheleg/dash-to-dock/issues #1002 https://github.com/micheleg/dash-to-dock/issues/1002 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1849928 Title: Dock stays ontop of Xscreensaver Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: Ubuntu 20.04 development version with kernel 5.3.0-18-generic up to date to latest @ 26/10/2019 The dock stays visible after Xscreensaver becomes active the screensaver flows under down the dock (see attachment) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-ubuntu-dock 67ubuntu19.10.1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 26 09:12:44 2019 InstallationDate: Installed on 2019-10-25 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191021) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1849928/+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
