[Desktop-packages] [Bug 1834138] Re: PA: Don't restore the streams to sinks/sources with only unavailable ports
I think this probably should be reworded: [Regression Potential] No, ... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1834138 Title: PA: Don't restore the streams to sinks/sources with only unavailable ports Status in HWE Next: New Status in OEM Priority Project: Confirmed Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Bionic: In Progress Status in pulseaudio source package in Disco: Fix Committed Status in pulseaudio source package in Eoan: Fix Released Bug description: SRU Document: [Impact] The Lenovo P520 machine has dual analogue codecs, so there are two sinks and two sources in the PA, one has the front headphone and front microphone, the other has the rear lineout, linein and rear microphone, and the rear microphone always shows up in the gnome- sound-setting, When we plug a microphone to front audio jack, there are two input devices: rear mic and front mic in the gnome-sound- setting, and suppose users select the the front mic to record sound via audio app like arecord, the front mic will be bond the arecord, after the front mic is unplugged, there is only one rear mic left in the gnome-sound-setting, but the binding will not be changed, the arecrod still bind to front mic, under this situation if users record sound via arecord, they will find they can't record any sound from any other input devices even they are listed in the gnome-sound-setting. This problem also happens to output devices too. [Test Case] After applying this patch, I did the same test: unplug the front mic, then use the arecord to record sound, the app can record sound from rear mic now. After I plug the front mic back, the arecord still record from front mic. Also did the similar test for output devices, it worked as expected too. [Regression Potential] No, Just make a simple check when creating new streams (sink_input/source_output), If the restored device (sink/source) has ports and all ports are unavialble, it will not restore the binding, otherwise it will work as before. [Other Info] No more info here To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1834138/+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 1837968] [NEW] GNOME Shell (X11) task switcher and LibreOffice
Public bug reported: Upgraded to 18.04.2 LTS (GNOME Shell 3.28.4/X11) from 16.04 LTS (Unity) and noticed that Alt-Tab task switcher doesn't update immediately with LibreOffice documents. Case in point: I've got LibreOffice, Firefox and a Nautilus window with a directory of LibreOffice spreadsheets open. When I Alt-Tab through this I see a generic LibreOffice icon, a Firefox icon (and its open windows) and a Nautilus icon. I'll then switch to the Nautilus window and open spreadsheet(s) and I see that LibreOffice has loaded them in the background behind the Nautilus window. Now when I Alt-Tab to switch to LibreOffice, there is not even a generic LibreOffice icon anymore. If I wait a few seconds and Alt-Tab again, I then see a LibreOffice Calc icon (and the open file windows). Update: I restarted using Wayland instead of X11 and the problem seems resolved, although LibreOffice defaults to a generic LO icon instead of a specific Writer/Calc/Draw/etc. icon in the switcher. But Wayland is not yet an option for me at present. Nevertheless it exists in GNOME Shell using X11. I haven't noticed similar behaviour with other programs with similar lags in the task switcher. This delay wasn't present (for me) before the upgrade/switch to GNOME Shell, so I'm assuming it's a Ubuntu/GNOME problem. I've also seen that similar problems have been reported in the past but for the most part they are quite old and I did not find this reported with the latest GNOME/Ubuntu 18.04LTS hence my new bug report. Thank you. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: 18.04lts gnome-shell libreoffice -- 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/1837968 Title: GNOME Shell (X11) task switcher and LibreOffice Status in gnome-shell package in Ubuntu: New Bug description: Upgraded to 18.04.2 LTS (GNOME Shell 3.28.4/X11) from 16.04 LTS (Unity) and noticed that Alt-Tab task switcher doesn't update immediately with LibreOffice documents. Case in point: I've got LibreOffice, Firefox and a Nautilus window with a directory of LibreOffice spreadsheets open. When I Alt-Tab through this I see a generic LibreOffice icon, a Firefox icon (and its open windows) and a Nautilus icon. I'll then switch to the Nautilus window and open spreadsheet(s) and I see that LibreOffice has loaded them in the background behind the Nautilus window. Now when I Alt-Tab to switch to LibreOffice, there is not even a generic LibreOffice icon anymore. If I wait a few seconds and Alt-Tab again, I then see a LibreOffice Calc icon (and the open file windows). Update: I restarted using Wayland instead of X11 and the problem seems resolved, although LibreOffice defaults to a generic LO icon instead of a specific Writer/Calc/Draw/etc. icon in the switcher. But Wayland is not yet an option for me at present. Nevertheless it exists in GNOME Shell using X11. I haven't noticed similar behaviour with other programs with similar lags in the task switcher. This delay wasn't present (for me) before the upgrade/switch to GNOME Shell, so I'm assuming it's a Ubuntu/GNOME problem. I've also seen that similar problems have been reported in the past but for the most part they are quite old and I did not find this reported with the latest GNOME/Ubuntu 18.04LTS hence my new bug report. Thank you. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1837968/+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 1836826] Re: Snaps not showing in categories due to store section name changes
** Changed in: gnome-software (Ubuntu Eoan) Status: Triaged => Fix Released ** Changed in: gnome-software (Ubuntu Eoan) Status: Fix Released => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1836826 Title: Snaps not showing in categories due to store section name changes Status in gnome-software package in Ubuntu: Fix Committed Status in gnome-software source package in Xenial: Triaged Status in gnome-software source package in Bionic: Triaged Status in gnome-software source package in Disco: Triaged Status in gnome-software source package in Eoan: Fix Committed Bug description: [Impact] The Snap Store changed the names of some of the sections. This means that these are no longer mapped to the XDG categories used in GNOME Software. See https://gitlab.gnome.org/GNOME/gnome-software/merge_requests/279 [Test Case] 1. Open GNOME Software 2. Go to graphics categeory. Expected result: Snaps are shown Observer result: Only .debs are shown [Regression Potential] Fix is just to change the name mappings, should be low risk. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1836826/+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 1830503] Re: [MSI B450 TOMAHAWK (MS-7C02), Realtek ALC892, Red Line Out, Rear] No sound at all
[Expired for alsa-driver (Ubuntu) because there has been no activity for 60 days.] ** Changed in: alsa-driver (Ubuntu) Status: Incomplete => Expired -- 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/1830503 Title: [MSI B450 TOMAHAWK (MS-7C02), Realtek ALC892, Red Line Out, Rear] No sound at all Status in alsa-driver package in Ubuntu: Expired Bug description: No sound Motherboard MSI B450 Tomahawnk CPU APU AMD Ryzen 5 2400G-4 Core RX Vega. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: inanna 1251 F pulseaudio /dev/snd/controlC0: inanna 1251 F pulseaudio /dev/snd/pcmC0D3p: inanna 1251 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun May 26 00:08:58 2019 InstallationDate: Installed on 2019-05-22 (3 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic_1 failed Symptom_Card: HD-Audio Generic - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: inanna 1251 F pulseaudio /dev/snd/controlC0: inanna 1251 F pulseaudio /dev/snd/pcmC0D3p: inanna 1251 F...m pulseaudio Symptom_Jack: Red Line Out, Rear Symptom_Type: No sound at all Title: [MS-7C02, Realtek ALC892, Red Line Out, Rear] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.40 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450 TOMAHAWK (MS-7C02) dmi.board.vendor: Micro-Star International Co., Ltd dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.40:bd12/19/2018:svnMicro-StarInternationalCo.,Ltd:pnMS-7C02:pvr1.0:rvnMicro-StarInternationalCo.,Ltd:rnB450TOMAHAWK(MS-7C02):rvr1.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C02 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1830503/+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 1830519] Re: firefox 67 keeps crashing on me
[Expired for firefox (Ubuntu) because there has been no activity for 60
days.]
** Changed in: firefox (Ubuntu)
Status: Incomplete => Expired
--
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/1830519
Title:
firefox 67 keeps crashing on me
Status in firefox package in Ubuntu:
Expired
Bug description:
A system that's been extremely good and stable has all of a sudden
become completely unusable after running Software Update.
After the last update, my system won't load firefox properly half of
the time. After loading pages like youtube it crashes the tab or just
crashes the entire browser. Sometimes it will immediately crash upon
launch and either restart the X server or just freeze.
I really don't know if it's firefox to blame or some kernel update.
My good system has become completely and totally unusable. Terribly
frustrating.
Ubuntu 18.04.2 LTS, firefox 67.0, core i7-2600, AMD Cedar graphics.
dmesg reports:
[ 139.743013] show_signal_msg: 36 callbacks suppressed
[ 139.743015] Web Content[2569]: segfault at 8021 ip 3e6b02233b3f sp
7ffd874d1988 error 4
[ 140.332634] apport[2683]: segfault at 8 ip 00572d98 sp
7fff0a7db4f0 error 6 in python3.6[40+3b2000]
[ 140.332651] Process 2683(apport) has RLIMIT_CORE set to 1
[ 140.332652] Aborting core
[ 162.224785] gnome-software[2707]: segfault at 55dca8ef8b68 ip
7f2ced519038 sp 7ffde7376160 error 4 in
libglib-2.0.so.0.5600.4[7f2ced4c4000+114000]
[ 221.530201] BUG: Bad page map in process IPC Launch #1 pte:696052845
pmd:78bfc6067
[ 221.530205] page:ba01da581480 count:0 mapcount:-1
mapping: index:0x0
[ 221.530208] flags: 0x17c010(dirty)
[ 221.530210] raw: 0017c010
fffe
[ 221.530212] raw: ba01da5814a0 ba01da5814a0
[ 221.530213] page dumped because: bad pte
[ 221.530215] addr:b80393c8 vm_flags:08100075
anon_vma:c17218bd mapping: (null) index:8cee1767
[ 221.530216] file: (null) fault: (null) mmap:
(null) readpage: (null)
[ 221.530218] CPU: 1 PID: 3113 Comm: IPC Launch #1 Not tainted
4.15.0-50-generic #54-Ubuntu
[ 221.530219] Hardware name: Hewlett-Packard HP Compaq 8200 Elite CMT
PC/1494, BIOS J01 v02.01 04/06/2011
[ 221.530220] Call Trace:
[ 221.530226] dump_stack+0x63/0x8b
[ 221.530228] print_bad_pte+0x222/0x2e0
[ 221.530230] unmap_page_range+0x881/0xd00
[ 221.530232] unmap_single_vma+0x7d/0xf0
[ 221.530233] unmap_vmas+0x51/0xb0
[ 221.530235] exit_mmap+0xb5/0x1c0
[ 221.530237] mmput+0x57/0x140
[ 221.530239] do_exit+0x295/0xb40
[ 221.530241] ? __do_page_fault+0x270/0x4d0
[ 221.530243] ? vfs_write+0x166/0x1a0
[ 221.530245] do_group_exit+0x43/0xb0
[ 221.530246] SyS_exit_group+0x14/0x20
[ 221.530248] do_syscall_64+0x73/0x130
[ 221.530257] entry_SYSCALL_64_after_hwframe+0x3d/0xa2
[ 221.530259] RIP: 0033:0x7fd2f674ae06
[ 221.530260] RSP: 002b:7fd2c8385518 EFLAGS: 0206 ORIG_RAX:
00e7
[ 221.530261] RAX: ffda RBX: 7fd2c420a540 RCX:
7fd2f674ae06
[ 221.530262] RDX: RSI: 003c RDI:
[ 221.530262] RBP: 7fd2c838552f R08: 00e7 R09:
ff58
[ 221.530263] R10: 0058 R11: 0206 R12:
03e8
[ 221.530264] R13: R14: 7fd2c83856e0 R15:
7fd2c420a540
[ 221.530265] Disabling lock debugging due to kernel taint
[ 221.535775] BUG: Bad rss-counter state mm:d3b63ddd idx:0 val:-1
[ 221.535779] BUG: Bad rss-counter state mm:d3b63ddd idx:1 val:1
[ 221.782881] BUG: Bad page map in process JS Helper pte:80069e0e6025
pmd:78a4ee067
[ 221.782886] page:ba01da783980 count:0 mapcount:-1
mapping: index:0x0
[ 221.782889] flags: 0x17c004(referenced)
[ 221.782891] raw: 0017c004
fffe
[ 221.782893] raw: ba01da7839a0 ba01da7839a0
[ 221.782894] page dumped because: bad pte
[ 221.782897] addr:9865cc11 vm_flags:0871 anon_vma:
(null) mapping:a5605d93 index:97
[ 221.782903] file:{d10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d}.xpi
fault:ext4_filemap_fault mmap:ext4_file_mmap readpage:ext4_readpage
[ 221.782906] CPU: 3 PID: 2951 Comm: JS Helper Tainted: GB
4.15.0-50-generic #54-Ubuntu
[ 221.782907] Hardware name: Hewlett-Packard HP Compaq 8200 Elite CMT
PC/1494, BIOS J01 v02.01 04/06/2011
[ 221.782908] Call Trace:
[ 221.782914] dump_stack+0x63/0x8b
[ 221.782916] print_bad_pte+0x222/0x2e0
[ 221.782918]
[Desktop-packages] [Bug 1837962] Re: Tap-to-Click of SYNA8005 touchpad (06CB:CD8C) failed to work after a while
** Also affects: libinput (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libinput in Ubuntu. https://bugs.launchpad.net/bugs/1837962 Title: Tap-to-Click of SYNA8005 touchpad (06CB:CD8C) failed to work after a while Status in libinput: Unknown Status in libinput package in Ubuntu: Fix Released Status in libinput source package in Bionic: New Status in libinput source package in Disco: Fix Released Status in libinput source package in Eoan: Fix Released Bug description: [Impact] 4.18+ kernel with Ubuntu 18.04. libinput 1.10.4-1 xserver-xorg-input-libinput 0.27.1-1 tap-to-click is on by default. After tapping on SYNA8005 (06CB:CD8C) for 50+ times, touchpad will be no response when tapping. [Fix] libinput detect these taps as palm, so permanently disable tap-to-click. upstream patch of libinput already fixed this issue: commit 237ebb7cc4e9bf035891176acb08b1bf558ee989 Author: Peter Hutterer Date: Mon Jun 25 14:50:22 2018 +1000 touchpad: don't disable tapping on MT_TOOL_PALM The tapping code can handle palm states now, so there is no need to disable tapping altogether when a tool-based palm is detected. Fixes https://gitlab.freedesktop.org/libinput/libinput/issues/65 Signed-off-by: Peter Hutterer [Test] Cherry-picked this commit to 1.10.4 and rebuild libinput, tested for thousands of times. touchpad taping OK. [Regression Potential] Low, upstream fix, tested OK. To manage notifications about this bug go to: https://bugs.launchpad.net/libinput/+bug/1837962/+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 1837962] Re: Tap-to-Click of SYNA8005 touchpad (06CB:CD8C) failed to work after a while
We need to add a bionic task here to track the fact the fix is missing in bionic. But since I've been told off for doing that in the past, someone else can do it :) ** Tags added: bionic ** Bug watch added: gitlab.freedesktop.org/libinput/libinput/issues #65 https://gitlab.freedesktop.org/libinput/libinput/issues/65 ** Also affects: libinput via https://gitlab.freedesktop.org/libinput/libinput/issues/65 Importance: Unknown Status: Unknown ** Tags added: fixed-in-1.11.901 fixed-upstream ** Also affects: libinput (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: libinput (Ubuntu Disco) Importance: Undecided Status: New ** Changed in: libinput (Ubuntu Disco) Status: New => Fix Released ** Changed in: libinput (Ubuntu Eoan) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libinput in Ubuntu. https://bugs.launchpad.net/bugs/1837962 Title: Tap-to-Click of SYNA8005 touchpad (06CB:CD8C) failed to work after a while Status in libinput: Unknown Status in libinput package in Ubuntu: Fix Released Status in libinput source package in Disco: Fix Released Status in libinput source package in Eoan: Fix Released Bug description: [Impact] 4.18+ kernel with Ubuntu 18.04. libinput 1.10.4-1 xserver-xorg-input-libinput 0.27.1-1 tap-to-click is on by default. After tapping on SYNA8005 (06CB:CD8C) for 50+ times, touchpad will be no response when tapping. [Fix] libinput detect these taps as palm, so permanently disable tap-to-click. upstream patch of libinput already fixed this issue: commit 237ebb7cc4e9bf035891176acb08b1bf558ee989 Author: Peter Hutterer Date: Mon Jun 25 14:50:22 2018 +1000 touchpad: don't disable tapping on MT_TOOL_PALM The tapping code can handle palm states now, so there is no need to disable tapping altogether when a tool-based palm is detected. Fixes https://gitlab.freedesktop.org/libinput/libinput/issues/65 Signed-off-by: Peter Hutterer [Test] Cherry-picked this commit to 1.10.4 and rebuild libinput, tested for thousands of times. touchpad taping OK. [Regression Potential] Low, upstream fix, tested OK. To manage notifications about this bug go to: https://bugs.launchpad.net/libinput/+bug/1837962/+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 1837962] [NEW] Tap-to-Click of SYNA8005 touchpad (06CB:CD8C) failed to work after a while
Public bug reported: [Impact] 4.18+ kernel with Ubuntu 18.04. libinput 1.10.4-1 xserver-xorg-input-libinput 0.27.1-1 tap-to-click is on by default. After tapping on SYNA8005 (06CB:CD8C) for 50+ times, touchpad will be no response when tapping. [Fix] libinput detect these taps as palm, so permanently disable tap-to-click. upstream patch of libinput already fixed this issue: commit 237ebb7cc4e9bf035891176acb08b1bf558ee989 Author: Peter Hutterer Date: Mon Jun 25 14:50:22 2018 +1000 touchpad: don't disable tapping on MT_TOOL_PALM The tapping code can handle palm states now, so there is no need to disable tapping altogether when a tool-based palm is detected. Fixes https://gitlab.freedesktop.org/libinput/libinput/issues/65 Signed-off-by: Peter Hutterer [Test] Cherry-picked this commit to 1.10.4 and rebuild libinput, tested for thousands of times. touchpad taping OK. [Regression Potential] Low, upstream fix, tested OK. ** Affects: libinput (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Tap-to-Click of SYNA8005 touchpad () failed to work after a while + Tap-to-Click of SYNA8005 touchpad (06CB:CD8C) failed to work after a while -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libinput in Ubuntu. https://bugs.launchpad.net/bugs/1837962 Title: Tap-to-Click of SYNA8005 touchpad (06CB:CD8C) failed to work after a while Status in libinput package in Ubuntu: New Bug description: [Impact] 4.18+ kernel with Ubuntu 18.04. libinput 1.10.4-1 xserver-xorg-input-libinput 0.27.1-1 tap-to-click is on by default. After tapping on SYNA8005 (06CB:CD8C) for 50+ times, touchpad will be no response when tapping. [Fix] libinput detect these taps as palm, so permanently disable tap-to-click. upstream patch of libinput already fixed this issue: commit 237ebb7cc4e9bf035891176acb08b1bf558ee989 Author: Peter Hutterer Date: Mon Jun 25 14:50:22 2018 +1000 touchpad: don't disable tapping on MT_TOOL_PALM The tapping code can handle palm states now, so there is no need to disable tapping altogether when a tool-based palm is detected. Fixes https://gitlab.freedesktop.org/libinput/libinput/issues/65 Signed-off-by: Peter Hutterer [Test] Cherry-picked this commit to 1.10.4 and rebuild libinput, tested for thousands of times. touchpad taping OK. [Regression Potential] Low, upstream fix, tested OK. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1837962/+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 1835144] Re: nvidia-340 340.107-0ubuntu0.16.04.2: nvidia kernel module failed to build
*** This bug is a duplicate of bug 1832000 *** https://bugs.launchpad.net/bugs/1832000 ** This bug has been marked a duplicate of bug 1832000 NVidia fails everytime a new kernel update is released : nvidia-340 340.107-0ubuntu0.16.04.2: nvidia kernel module failed to build -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1835144 Title: nvidia-340 340.107-0ubuntu0.16.04.2: nvidia kernel module failed to build Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: fails to build after kernel update. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: nvidia-340 340.107-0ubuntu0.16.04.2 ProcVersionSignature: Ubuntu 4.4.0-154.181-generic 4.4.179 Uname: Linux 4.4.0-154-generic x86_64 NonfreeKernelModules: nvidia_uvm 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.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.107 Thu May 24 21:54:01 PDT 2018 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.11) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None DKMSKernelVersion: 4.4.0-154-generic Date: Tue Jul 2 22:07:56 2019 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GT216 [GeForce GT 220] [10de:0a20] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GT216 [GeForce GT 220] [1462:1910] InstallationDate: Installed on 2015-11-14 (1326 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: HP-Pavilion AY600AA-ABA HPE-127c PackageVersion: 340.107-0ubuntu0.16.04.2 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-154-generic root=UUID=55fcadff-651e-d101-002c-a5ff651ed101 ro quiet splash nomodeset usbcore.autosuspend=-1 RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.32 SourcePackage: nvidia-graphics-drivers-340 Title: nvidia-340 340.107-0ubuntu0.16.04.2: nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.07 dmi.board.name: IONA dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.07:bd12/21/2009:svnHP-Pavilion:pnAY600AA-ABAHPE-127c:pvr:rvnMSI:rnIONA:rvr1.0:cvnHewlett-Packard:ct3:cvr: dmi.product.name: AY600AA-ABA HPE-127c dmi.sys.vendor: HP-Pavilion modified.conffile..etc.modprobe.d.nvidia-340_hybrid.conf: [deleted] version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Tue Jul 2 22:21:47 2019 xserver.configfile: default xserver.errors: open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1835144/+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 1837827] Re: nvidia-340 340.107-0ubuntu0.16.04.2: nvidia kernel module failed to build
*** This bug is a duplicate of bug 1832000 *** https://bugs.launchpad.net/bugs/1832000 ** This bug has been marked a duplicate of bug 1835144 nvidia-340 340.107-0ubuntu0.16.04.2: nvidia kernel module failed to build ** This bug is no longer a duplicate of bug 1835144 nvidia-340 340.107-0ubuntu0.16.04.2: nvidia kernel module failed to build ** This bug has been marked a duplicate of bug 1832000 NVidia fails everytime a new kernel update is released : nvidia-340 340.107-0ubuntu0.16.04.2: nvidia kernel module failed to build -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1837827 Title: nvidia-340 340.107-0ubuntu0.16.04.2: nvidia kernel module failed to build Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: nvidia-340 340.107-0ubuntu0.16.04.2: nvidia kernel module failed to build ProblemType: Package DistroRelease: Ubuntu 16.04 Package: nvidia-340 340.107-0ubuntu0.16.04.2 ProcVersionSignature: Ubuntu 4.4.0-154.181-generic 4.4.179 Uname: Linux 4.4.0-154-generic x86_64 NonfreeKernelModules: nvidia_uvm 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.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.107 Thu May 24 21:54:01 PDT 2018 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.11) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None DKMSKernelVersion: 4.4.0-157-generic Date: Wed Jul 24 22:46:10 2019 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GT216 [GeForce GT 220] [10de:0a20] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GT216 [GeForce GT 220] [1462:1910] InstallationDate: Installed on 2015-11-14 (1348 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: HP-Pavilion AY600AA-ABA HPE-127c PackageVersion: 340.107-0ubuntu0.16.04.2 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-154-generic root=UUID=55fcadff-651e-d101-002c-a5ff651ed101 ro quiet splash nomodeset usbcore.autosuspend=-1 RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.32 SourcePackage: nvidia-graphics-drivers-340 Title: nvidia-340 340.107-0ubuntu0.16.04.2: nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.07 dmi.board.name: IONA dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.07:bd12/21/2009:svnHP-Pavilion:pnAY600AA-ABAHPE-127c:pvr:rvnMSI:rnIONA:rvr1.0:cvnHewlett-Packard:ct3:cvr: dmi.product.name: AY600AA-ABA HPE-127c dmi.sys.vendor: HP-Pavilion modified.conffile..etc.modprobe.d.nvidia-340_hybrid.conf: [deleted] version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Wed Jul 24 21:47:47 2019 xserver.configfile: default xserver.errors: open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1837827/+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 1734541] Re: encrypted home-directory is not unmounted on logout
** Tags removed: artful ** Tags added: xenial -- 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/1734541 Title: encrypted home-directory is not unmounted on logout Status in GNOME Session Shutdown: New Status in ecryptfs-utils package in Ubuntu: Confirmed Status in gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Bug description: Current Situation: If you log out from an user account with an encrypted home directory, it is not automatically unmounted and encrypted again. Expected behaviour: If I log out from an user account with an encrypted home directory, Id expect the homedir to be unmounted and encrypted again. Stepts to reproduce: log into an account with encrypted home directory. (lets call it: user) Log out again log into another account (which has sudo rights, lets call it: user2) and now enter the following into a terminal: user2@ubuntu: sudo su user2@ubuntu: ls -la /home/user you can see the files of the user Reasons: This is a security issue, because as a user you can reasonable expect your data to be safe, if you log out. if you would simply log in as another user but keep your data accessable you would simply switch user, instead of loggin out. Many users only suspend their laptop while carrying it with them. Logging out and suspending the user expects to have at least the home directory encrypted. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gdm3 3.26.1-3ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Nov 26 16:18:39 2017 EcryptfsInUse: Yes ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-session-shutdown/+bug/1734541/+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 1164016] Re: restore type-ahead find
This change has made the system effectively inappropriate for use in a business situation where mistakes are to be avoided. In the old system, searching within a folder for a file to send to a client would only list files from that folder. Now, file-open and so on show me files from ANYWHERE ON THE SYSTEM FOR ANY CLIENT WHATSOEVER, leaving the user a single mis-click away from a GDPR violation. Choosing a folder should set a boundary on the files displayed. If I want search, I'll search. -- 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/1164016 Title: restore type-ahead find Status in Nautilus: Expired Status in nautilus package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Bug description: GNOME removed type-ahead find in Nautilus 3.6, not without controversy: https://mail.gnome.org/archives/nautilus- list/2012-August/msg2.html Now when you type in a Nautilus window, Nautilus immediately performs a search in the current directory and all its subdirectories. I personally find this annoying. If I want to search, I'll click the search icon. Often I'm looking at a long directory listing and simply want to jump to a certain point in it, and type-ahead find works great for that. Would Ubuntu consider patching type-ahead find back in? To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1164016/+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 1828102] Re: Regression in ModemManager
@till-kamppeter are you able to verify this for disco? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1828102 Title: Regression in ModemManager Status in modemmanager package in Ubuntu: Fix Released Status in modemmanager source package in Bionic: Fix Released Status in modemmanager source package in Cosmic: Won't Fix Status in modemmanager source package in Disco: Fix Committed Status in modemmanager source package in Eoan: Fix Released Bug description: [Impact] ModemManager disconnects from CDMA modem after 30 sec failing to check signal status due to incorrect error handling [Test case] connect to a cdma device without an extra AT channel (Eg. Samsung brightside phone) and modemmanager will terminate the connection [Regression potential] The patch is tiny, fixing an obvious overlook, and it only affects CDMA broadband modems, so the risk of a regression is very low. [Original description] ModemManager disconnects after ~30 sec caused by a typo in 1.8 see https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1819615 and https://gitlab.freedesktop.org/mobile-broadband/ModemManager/issues/119 for details needs a SRU for cosmic and dingo patch attached yechiel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1828102/+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 1734541] Re: encrypted home-directory is not unmounted on logout
** Also affects: gnome-session-shutdown Importance: Undecided Status: New -- 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/1734541 Title: encrypted home-directory is not unmounted on logout Status in GNOME Session Shutdown: New Status in ecryptfs-utils package in Ubuntu: Confirmed Status in gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Bug description: Current Situation: If you log out from an user account with an encrypted home directory, it is not automatically unmounted and encrypted again. Expected behaviour: If I log out from an user account with an encrypted home directory, Id expect the homedir to be unmounted and encrypted again. Stepts to reproduce: log into an account with encrypted home directory. (lets call it: user) Log out again log into another account (which has sudo rights, lets call it: user2) and now enter the following into a terminal: user2@ubuntu: sudo su user2@ubuntu: ls -la /home/user you can see the files of the user Reasons: This is a security issue, because as a user you can reasonable expect your data to be safe, if you log out. if you would simply log in as another user but keep your data accessable you would simply switch user, instead of loggin out. Many users only suspend their laptop while carrying it with them. Logging out and suspending the user expects to have at least the home directory encrypted. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gdm3 3.26.1-3ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Nov 26 16:18:39 2017 EcryptfsInUse: Yes ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-session-shutdown/+bug/1734541/+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 1837945] [NEW] AMD RX 570 Black Screen at boot
Public bug reported: Ubuntu 19.04 Problem: Booting from live media OR installed ubuntu fails with a blank, black screen and total system hang. How to reproduce: Using AMDGpu driver and AMD 4th Gen GCN GPU, try to boot Ubuntu 19.04 (or 18.04) Resolution: Manually updating kernel to 5.1 and adding the "amdgpu.dc=0" kernel boot parameter seems to fix the problem. inxi -SGxxx Output: System: Host: Kernel: 5.1.0-050100-generic x86_64 bits: 64 compiler: gcc v: 8.3.0 Desktop: Gnome 3.32.1 wm: gnome-shell dm: GDM3 3.32.0 Distro: Ubuntu 19.04 (Disco Dingo) Graphics: Device-1: AMD Ellesmere [Radeon RX 470/480/570/570X/580/580X] driver: amdgpu v: kernel bus ID: 07:00.0 chip ID: 1002:67df Display: x11 server: X.Org 1.20.4 driver: ati,fbdev unloaded: modesetting,radeon,vesa compositor: gnome-shell resolution: 1920x1080~60Hz OpenGL: renderer: Radeon RX 570 Series (POLARIS10 DRM 3.30.0 5.1.0-050100-generic LLVM 8.0.0) v: 4.5 Mesa 19.0.2 direct render: Yes ** Affects: xserver-xorg-video-amdgpu (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1837945 Title: AMD RX 570 Black Screen at boot Status in xserver-xorg-video-amdgpu package in Ubuntu: New Bug description: Ubuntu 19.04 Problem: Booting from live media OR installed ubuntu fails with a blank, black screen and total system hang. How to reproduce: Using AMDGpu driver and AMD 4th Gen GCN GPU, try to boot Ubuntu 19.04 (or 18.04) Resolution: Manually updating kernel to 5.1 and adding the "amdgpu.dc=0" kernel boot parameter seems to fix the problem. inxi -SGxxx Output: System: Host: Kernel: 5.1.0-050100-generic x86_64 bits: 64 compiler: gcc v: 8.3.0 Desktop: Gnome 3.32.1 wm: gnome-shell dm: GDM3 3.32.0 Distro: Ubuntu 19.04 (Disco Dingo) Graphics: Device-1: AMD Ellesmere [Radeon RX 470/480/570/570X/580/580X] driver: amdgpu v: kernel bus ID: 07:00.0 chip ID: 1002:67df Display: x11 server: X.Org 1.20.4 driver: ati,fbdev unloaded: modesetting,radeon,vesa compositor: gnome-shell resolution: 1920x1080~60Hz OpenGL: renderer: Radeon RX 570 Series (POLARIS10 DRM 3.30.0 5.1.0-050100-generic LLVM 8.0.0) v: 4.5 Mesa 19.0.2 direct render: Yes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1837945/+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 1837941] [NEW] Update to 68.0.1
Public bug reported: See https://www.mozilla.org/en-US/firefox/68.0.1/releasenotes/ ** Affects: firefox (Ubuntu) Importance: Undecided Status: Fix Released ** Changed in: firefox (Ubuntu) Status: New => Fix Released -- 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/1837941 Title: Update to 68.0.1 Status in firefox package in Ubuntu: Fix Released Bug description: See https://www.mozilla.org/en-US/firefox/68.0.1/releasenotes/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1837941/+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 1837902] Re: Ubuntu Software doesn't show any update description
Thank you for making ubuntu better! When filing bugs please use ubuntu-bug packagename you can still collect your info with: apport-collect bugID so revelant info adds to your bug and developers can debug a better way ** Changed in: gnome-software (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1837902 Title: Ubuntu Software doesn't show any update description Status in gnome-software package in Ubuntu: Incomplete Bug description: When Ubuntu releases an update the only information I get in Ubuntu Software is the one shown in the attached screenshot: no list of updates packages at all. Similarly, after clicking on the Update button, only a tiny progress bar is shown, it's never clear what is being done. I remember having used gnome-software in Fedora and the update process was more informative. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1837902/+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 1790979] Re: Unable to change disk decryption passphrase
*** This bug is a duplicate of bug 1837437 *** https://bugs.launchpad.net/bugs/1837437 ** This bug has been marked a duplicate of bug 1837437 disk content permanently lost when changing LUKS password -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1790979 Title: Unable to change disk decryption passphrase Status in gnome-disk-utility package in Ubuntu: Confirmed Status in gnome-disk-utility package in Arch Linux: New Bug description: Versions: Ubuntu 18.04 LTS gnome-disk-utility 3.28.3-0ubuntu1~18.04.1 -- What I'm trying to do: Change the disk decryption passphrase of key in any slot other than slot 0 while there is an existing key in slot 0 (e.g. changing the disk decryption passphrase of slot 1) using gnome-disk-utility. Ran "Disks" > Selected my encrypted device partition > Clicked the gear icon > Selected "Change passphrase" > Entered the passphrase I wanted to change > Entered the passphrase I wanted to change to and confirmed it > clicked "Change". -- What I expected to happen: After clicking "Change" I expected to get no errors and have the passphrase I wanted to change to be valid to decrypt the disk. In the event of an error I expected the passphrase I was trying to change to still be valid to decrypt the disk. -- What is happening: I get an error message pop-up: Error changing passphrase Error changing passphrase on device /dev/sda2/:Failed to add the new passphrase: Invalid argument (udisks-error-quark, 0) And the key that I was trying to change gets deleted with no new key being added. -- (Before trying to change passphrase in key slot 2 using gnome-disk- utility) sudo cryptsetup luksDump /dev/sda2 LUKS header information for /dev/sda2 Version: 1 Cipher name: aes Cipher mode: cbc-essiv:sha256 Hash spec:sha1 Payload offset: 4096 MK bits: 256 MK digest:0f 5d 66 ec 16 0b 0c f2 4b 0a 9f 99 28 41 59 64 e9 9d 75 64 MK salt: 89 e5 16 e5 e0 5d f5 63 f6 ba 2b f1 df e8 e6 1d 11 52 27 39 ff 87 4c 70 ab b7 49 a2 97 e0 46 41 MK iterations:101875 UUID: c5754fe4-0835-431f-996b-e2202c380d05 Key Slot 0: ENABLED Iterations: 42 Salt: cb 25 fd 7d 14 ca af f1 6a 57 b9 b7 b8 7a 45 76 9e 9b 3f ef 6a 3a e7 f6 18 24 7a 6e bb 0d 36 78 Key material offset:8 AF stripes: 4000 Key Slot 1: ENABLED Iterations: 2074334 Salt: c2 cc 91 12 25 f4 80 21 d2 fa 91 44 ef 02 04 3e 6d d8 85 ef b2 39 fb c2 94 f1 62 ee db 79 3c ed Key material offset:264 AF stripes: 4000 Key Slot 2: ENABLED Iterations: 2090878 Salt: 47 fa 77 b7 f8 31 dc 48 ab 58 f7 25 a4 d5 c7 be 35 a3 83 6a 4d 1d bb 24 1c 38 12 2d f1 15 40 7f Key material offset:520 AF stripes: 4000 Key Slot 3: DISABLED Key Slot 4: DISABLED Key Slot 5: DISABLED Key Slot 6: DISABLED Key Slot 7: DISABLED -- (After trying to change passphrase in key slot 2 using gnome-disk- utility) sudo cryptsetup luksDump /dev/sda2 LUKS header information for /dev/sda2 Version: 1 Cipher name: aes Cipher mode: cbc-essiv:sha256 Hash spec:sha1 Payload offset: 4096 MK bits: 256 MK digest:0f 5d 66 ec 16 0b 0c f2 4b 0a 9f 99 28 41 59 64 e9 9d 75 64 MK salt: 89 e5 16 e5 e0 5d f5 63 f6 ba 2b f1 df e8 e6 1d 11 52 27 39 ff 87 4c 70 ab b7 49 a2 97 e0 46 41 MK iterations:101875 UUID: c5754fe4-0835-431f-996b-e2202c380d05 Key Slot 0: ENABLED Iterations: 42 Salt: cb 25 fd 7d 14 ca af f1 6a 57 b9 b7 b8 7a 45 76 9e 9b 3f ef 6a 3a e7 f6 18 24 7a 6e bb 0d 36 78 Key material offset:8 AF stripes: 4000 Key Slot 1: ENABLED Iterations: 2074334 Salt: c2 cc 91 12 25 f4 80 21 d2 fa 91 44 ef 02 04 3e 6d d8 85 ef b2 39 fb c2 94 f1 62 ee db 79 3c ed Key material offset:264 AF stripes: 4000 Key Slot 2: DISABLED Key Slot 3: DISABLED Key Slot 4: DISABLED Key Slot 5: DISABLED Key Slot 6: DISABLED Key Slot
[Desktop-packages] [Bug 1837068] Re: libssh armhf autopkgtest failure on valgrind unhandled instruction: 0xEBAD 0x1CCA
oh, except not exactly due to a change in libssl, because in the same time period, libssh 0.8.7-1 autopkgtests still pass and libssh 0.9.0-1 fail. Still looking. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libssh in Ubuntu. https://bugs.launchpad.net/bugs/1837068 Title: libssh armhf autopkgtest failure on valgrind unhandled instruction: 0xEBAD 0x1CCA Status in libssh package in Ubuntu: New Status in valgrind package in Ubuntu: New Bug description: The libssh 0.9 armhf eoan tests are failing http://autopkgtest.ubuntu.com/packages/libs/libssh/eoan/armhf The error is 'disInstr(thumb): unhandled instruction: 0xEBAD 0x1CCA ==1127== valgrind: Unrecognised instruction at address 0x4b9c93d. ==1127==at 0x4B9C93C: ??? (in /usr/lib/arm-linux-gnueabihf/libcrypto.so.1.1)' Looking upstream to valgrind bug there is one matching with an (unreviewed) patch https://bugs.kde.org/show_bug.cgi?id=385262 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libssh/+bug/1837068/+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 1837068] Re: libssh armhf autopkgtest failure on valgrind unhandled instruction: 0xEBAD 0x1CCA
The regression appears to be caused by a change in libssl, not in libssh or valgrind, therefore the autopkgtest regression is already present in the release pocket and the failure should be marked as a bad test. ** Tags removed: rls-ee-incoming ** Tags added: rls-ee-notfixing -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libssh in Ubuntu. https://bugs.launchpad.net/bugs/1837068 Title: libssh armhf autopkgtest failure on valgrind unhandled instruction: 0xEBAD 0x1CCA Status in libssh package in Ubuntu: New Status in valgrind package in Ubuntu: New Bug description: The libssh 0.9 armhf eoan tests are failing http://autopkgtest.ubuntu.com/packages/libs/libssh/eoan/armhf The error is 'disInstr(thumb): unhandled instruction: 0xEBAD 0x1CCA ==1127== valgrind: Unrecognised instruction at address 0x4b9c93d. ==1127==at 0x4B9C93C: ??? (in /usr/lib/arm-linux-gnueabihf/libcrypto.so.1.1)' Looking upstream to valgrind bug there is one matching with an (unreviewed) patch https://bugs.kde.org/show_bug.cgi?id=385262 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libssh/+bug/1837068/+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 1829838] Re: 1.10.14-0ubuntu2 breaks DNS propagation from VPN
** Attachment added: "log-network-manager-with-segmentation.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829838/+attachment/5279222/+files/log-network-manager-with-segmentation.txt -- 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/1829838 Title: 1.10.14-0ubuntu2 breaks DNS propagation from VPN Status in network-manager package in Ubuntu: Incomplete Bug description: I have an OpenVPN connection, and I use the update-systemd-resolved to correctly fetch the DNS from the VPN. The issue arose updating my Ubuntu 18.04: the script is no longer invoked, and even invoking it manually (sudo openvpn myfile.ovpn) does not work anymore, even if in that case systemd-resolve --status shows the new DNS on the interface correctly. As suggested in https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/120/comments/99, reverting to 1.10.6-2ubuntu1.1 fixes the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829838/+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 1829838] Re: 1.10.14-0ubuntu2 breaks DNS propagation from VPN
** Attachment added: "log-network-manager-without-segmentation.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829838/+attachment/5279221/+files/log-network-manager-without-segmentation.txt -- 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/1829838 Title: 1.10.14-0ubuntu2 breaks DNS propagation from VPN Status in network-manager package in Ubuntu: Incomplete Bug description: I have an OpenVPN connection, and I use the update-systemd-resolved to correctly fetch the DNS from the VPN. The issue arose updating my Ubuntu 18.04: the script is no longer invoked, and even invoking it manually (sudo openvpn myfile.ovpn) does not work anymore, even if in that case systemd-resolve --status shows the new DNS on the interface correctly. As suggested in https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/120/comments/99, reverting to 1.10.6-2ubuntu1.1 fixes the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829838/+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 1836462] Re: Renaming Templates to # Templates fixes speed issues present in wide range of desktop applications
*** This bug is a duplicate of bug 1837783 *** https://bugs.launchpad.net/bugs/1837783 ** This bug has been marked a duplicate of bug 1837783 Scrolling can be improved a lot -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-user-dirs in Ubuntu. https://bugs.launchpad.net/bugs/1836462 Title: Renaming Templates to # Templates fixes speed issues present in wide range of desktop applications Status in xdg-user-dirs package in Ubuntu: New Status in xdg-user-dirs package in Fedora: Unknown Bug description: Renaming "Templates" to "# Templates" fixes a lot of speed issues in a range of desktop applications, e.g. file managers, text editors, etc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-user-dirs/+bug/1836462/+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 1837437] Re: disk content permanently lost when changing LUKS password
I sponsored it, thanks! (Also, Scenarii, nice)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libblockdev in Ubuntu.
https://bugs.launchpad.net/bugs/1837437
Title:
disk content permanently lost when changing LUKS password
Status in libblockdev package in Ubuntu:
Fix Released
Status in libblockdev source package in Disco:
Confirmed
Status in gnome-disk-utility package in Debian:
Unknown
Bug description:
[Impact]
Users with full disk encryption trying to change the encryption
passphrase in gnome-disks will get an error message, and after
rebooting neither the old passphrase nor the new one can unlock their
disk, rendering the machine unusable.
[Test Case]
(can be done in a virtual machine, for testing purposes)
1. Download a 19.04 ISO, and install it, choosing the full disk encryption
option
2. When rebooting after the installation is complete, you are prompted for
your passphrase to unlock the disk
3. Once logged in, open gnome-disks, select the encrypted disk and click the
contextual action to change the encryption passphrase
4. Enter your old passphrase and the new one (twice), as prompted, then click
OK
Expected result: the passphrase is changed successfully, and when
rebooting the new passphrase can unlock the disk
Current result: changing the passphrase fails, the user is presented
with an error message ("Error changing passphrase on device /dev/sda5:
Failed to add the new passphrase: Invalid argument (udisks-error-
quark, 0)"), and when rebooting neither the old passphrase nor the new
one can unlock the disk, which renders it unusable
To test the fix, the updated libblockdev* packages need to be
installed on the machine before attempting to change the encryption
passphrase in gnome-disks.
[Regression Potential]
The patch only touches code related to changing the LUKS encryption
passphrase, so non-encrypted disk setups should not be affected.
Scenarii with full-disk encryption should be carefully tested, including
changing an existing passphrase, adding and removing passphrases, both from the
gnome-disks UI and using the cryptsetup CLI.
[Original Description]
This is fixed upstream. Logging this bug to track the fix in to
Ubuntu.
From the upstream bug:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928893
Dear Maintainer,
* What led up to the situation?
Install system using normal full disk encryption LUKS+Ext4.
After install open gnome-disk-utility and change
encryption password. It gives some error dialog and
now you are royally screwed. It deleted the only
LUKS keyslot. Cannot add new keyslots because of that.
All data will be lost after reboot.
Here is output of luksdump:
udo cryptsetup luksDump /dev/sda5
LUKS header information
Version: 2
Epoch: 4
Metadata area: 16384 [bytes]
Keyslots area: 1678 [bytes]
UUID: 3c16ad4c-294c-4547-bf3e-bb8864ba5ea3
Label: (no label)
Subsystem: (no subsystem)
Flags: (no flags)
Data segments:
0: crypt
offset: 16777216 [bytes]
length: (whole device)
cipher: aes-xts-plain64
sector: 512 [bytes]
Keyslots:
Tokens:
Digests:
0: pbkdf2
Hash: sha256
Iterations: 59904
Salt: XX XX XX XX XX
Digest: XX XX XX XX XX ...
I changed salt and digest. No Keyslots are present!!!
I tried this 2 times in a row with new install,
exactly same result.
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.0.8-xanmod5 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8),
LANGUAGE=ru_RU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages gnome-disk-utility depends on:
ii dconf-gsettings-backend [gsettings-backend] 0.30.1-2
ii libatk1.0-0 2.30.0-2
ii libc6 2.28-10
ii libcairo2 1.16.0-4
ii libcanberra-gtk3-0 0.30-7
ii libdvdread4 6.0.1-1
ii libgdk-pixbuf2.0-0 2.38.1+dfsg-1
ii libglib2.0-0 2.58.3-1
ii libgtk-3-0 3.24.5-1
ii liblzma5 5.2.4-1
ii libnotify4 0.7.7-4
ii libpango-1.0-0 1.42.4-6
ii libpangocairo-1.0-0 1.42.4-6
ii libpwquality1 1.4.0-3
ii libsecret-1-0 0.18.7-1
ii libsystemd0 241-3
ii libudisks2-0 2.8.1-4
ii udisks2 2.8.1-4
gnome-disk-utility recommends no packages.
gnome-disk-utility suggests no packages.
-- no debconf information
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libblockdev/+bug/1837437/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe :
[Desktop-packages] [Bug 1837907] [NEW] /usr/lib/chromium-browser/chromium-browser:5:operator:~LogMessage:OnConnectionDisconnectedFilter:dbus_connection_dispatch:dbus::Bus::ProcessAllIncomingDataIfAny
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding chromium-browser. This problem was most recently seen with package version 75.0.3770.90-0ubuntu0.19.04.1, the problem page at https://errors.ubuntu.com/problem/843d8a8ce4bc8f6301b5fde1ed97d345ef3e2bde contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: bionic cosmic disco kylin-18.04 kylin-18.10 xenial -- 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/1837907 Title: /usr/lib/chromium-browser/chromium- browser:5:operator:~LogMessage:OnConnectionDisconnectedFilter:dbus_connection_dispatch:dbus::Bus::ProcessAllIncomingDataIfAny Status in chromium-browser package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding chromium-browser. This problem was most recently seen with package version 75.0.3770.90-0ubuntu0.19.04.1, the problem page at https://errors.ubuntu.com/problem/843d8a8ce4bc8f6301b5fde1ed97d345ef3e2bde contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1837907/+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 1835936] Re: gnome-control-center crash ubuntu 18.04.2
Today after taking snapshots with Timeshift, I upgraded VirtualBox from 10.0.8 to 10.0.10 and also upgraded the Guest Additions to the same version. I then upgraded Ubuntu 18.04 to the latest patches as of today, INCLUDING the two mutter-2 patches that were causing the GUI login not to appear after a reboot. The system was rebooted after the installation of the patches above, and the GUI login came up as it normally should. As far as I'm concerned, this bug can be CLOSED. Thank you. -- 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/1835936 Title: gnome-control-center crash ubuntu 18.04.2 Status in gnome-control-center package in Ubuntu: Invalid Bug description: Ubuntu 18.04.02 fresh installed on Virtualbox 6.0.8 including Guest Additions on host Mac Pro running 10.14.5 Mojave in April 2019. Ubuntu system has latest patches EXCEPT mutter-2 (which cause login GUI to fail after reboot). crash logs for gnome-control-center, gnome-shell and seahorse attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1835936/+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 1829838] Re: 1.10.14-0ubuntu2 breaks DNS propagation from VPN
Jean, thank you for the input, could you retest these two cases (with and without split connection) but create debug logs of Network Manager and systemd-resolved, following the instructions on https://wiki.ubuntu.com/DebuggingNetworkManager (and/or of my comment #10)? -- 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/1829838 Title: 1.10.14-0ubuntu2 breaks DNS propagation from VPN Status in network-manager package in Ubuntu: Incomplete Bug description: I have an OpenVPN connection, and I use the update-systemd-resolved to correctly fetch the DNS from the VPN. The issue arose updating my Ubuntu 18.04: the script is no longer invoked, and even invoking it manually (sudo openvpn myfile.ovpn) does not work anymore, even if in that case systemd-resolve --status shows the new DNS on the interface correctly. As suggested in https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/120/comments/99, reverting to 1.10.6-2ubuntu1.1 fixes the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829838/+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 1682193] Re: Mouse acceleration significantly reduced after upgrade to 17.04
This bug report expired because 17.04 is not supported anymore. Did anyone recreate a corresponding bug report for a more recent version of Ubuntu? If so, can you please publish the link so we can subscribe to it? -- 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/1682193 Title: Mouse acceleration significantly reduced after upgrade to 17.04 Status in xorg package in Ubuntu: Won't Fix Bug description: My external Logitech USB mouse was behaving nicely under 16.10 but after upgrade to 17.04 it has slowed down to a crawl. Settings slidebars are set at the maximum acceleration, but it only affects the touch pad, the mouse is extremely slow. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1682193/+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 1697958] Re: HPLIP cannot detect printers in your network
Oh, and what exactly is a "systemtray?" All of a sudden, for the past year or so, the HP p1102w Pro has been eliciting an HPLIP error message saying that there is no "systemtray" and so it was stopping. I have no idea what a systemtray is. I obviously didn't lose a systemtray that was once there--all is like new in my old printer. Windows' driver makes no complaint about a systemtray but HPLIP in Linux is obsessed by it and the danger caused by it being missing. I don't want to be forced to go into Windows in order to print something. I have used Linux since 1997 and I don't want to have Linux suddenly fail to support my perfectly fine older HP printer that has been working fine under Linux for years. Because I'm annoyed at how much effort I've put into making this perfectly fine printer work with the latest versions of Linux and HPLIP I've considered buying another inexpensive printer but I'm not sure how well that will work out in Linux. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1697958 Title: HPLIP cannot detect printers in your network Status in HPLIP: New Status in hplip package in Ubuntu: Confirmed Bug description: On a fresh install of Kubuntu 17.04 I cannot add a network printer though the HPLIP Toolbox. I get an error message that says "HPLIP cannot detect printers in your network. This may be due to existing firewall settings blocking the required ports. When you are in a trusted network environment, you may open the ports for network services like mdns and slp in the firewall. For detailed steps follow the link. http://hplipopensource.com/node/374; However snmpwalk finds the printer perfectly fine $ snmpwalk -Os -c public -v 1 192.168.1.21 1.3.6.1.4.1.11.2.3.9.1.1.7.0 iso.3.6.1.4.1.11.2.3.9.1.1.7.0 = STRING: "MFG:Hewlett-Packard;CMD:PJL,PML,PCLXL,URP,PCL,PDF,POSTSCRIPT;MDL:HP LaserJet 200 colorMFP M276nw;CLS:PRINTER;DES:Hewlett-Packard LaserJet 200 colorMFP M276nw;MEM:MEM=230MB;COMMENT:RES=600x8;LEDMDIS:USB#ff#04#01;CID:HPLJPDLV1;" Other systems that were upgraded to 17.04 can still access and detect the printer. What I expect to happen: 1. Open HPLIP Toolbox 2. Add a network printer 3. Printer is detected What happened instead 1. Open HPLIP Toolbox 2. Add a network printer 3. No printers found ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: hplip-gui 3.16.11+repack0-2 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 CurrentDesktop: KDE Date: Wed Jun 14 11:23:50 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-06-09 (4 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Lpstat: device for Hewlett-Packard-HP-LaserJet-P1505: implicitclass:Hewlett-Packard-HP-LaserJet-P1505 device for HP-LaserJet-200-colorMFP-M276nw: ipp://NPI62B4B3.local:631/ipp/print Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0aa7 Intel Corp. Bus 001 Device 002: ID 1bcf:2c87 Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Pavilion Notebook PackageArchitecture: all Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP-LaserJet-200-colorMFP-M276nw.ppd', '/etc/cups/ppd/Hewlett-Packard-HP-LaserJet-P1505.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP-LaserJet-200-colorMFP-M276nw.ppd: Permission denied grep: /etc/cups/ppd/Hewlett-Packard-HP-LaserJet-P1505.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic.efi.signed root=UUID=e56bcb4e-c73e-4581-9f09-4ef3fe063e74 ro quiet splash vt.handoff=7 SourcePackage: hplip UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.36 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8215 dmi.board.vendor: HP dmi.board.version: 83.15 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.36:bd04/07/2017:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn8215:rvr83.15:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/1697958/+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 1837902] Re: Ubuntu Software doesn't show any update description
** Attachment added: "Screenshot from 2019-07-25 10-40-00.png" https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1837902/+attachment/5279216/+files/Screenshot%20from%202019-07-25%2010-40-00.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1837902 Title: Ubuntu Software doesn't show any update description Status in gnome-software package in Ubuntu: New Bug description: When Ubuntu releases an update the only information I get in Ubuntu Software is the one shown in the attached screenshot: no list of updates packages at all. Similarly, after clicking on the Update button, only a tiny progress bar is shown, it's never clear what is being done. I remember having used gnome-software in Fedora and the update process was more informative. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1837902/+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 1837902] [NEW] Ubuntu Software doesn't show any update description
Public bug reported: When Ubuntu releases an update the only information I get in Ubuntu Software is the one shown in the attached screenshot: no list of updates packages at all. Similarly, after clicking on the Update button, only a tiny progress bar is shown, it's never clear what is being done. I remember having used gnome-software in Fedora and the update process was more informative. ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1837902 Title: Ubuntu Software doesn't show any update description Status in gnome-software package in Ubuntu: New Bug description: When Ubuntu releases an update the only information I get in Ubuntu Software is the one shown in the attached screenshot: no list of updates packages at all. Similarly, after clicking on the Update button, only a tiny progress bar is shown, it's never clear what is being done. I remember having used gnome-software in Fedora and the update process was more informative. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1837902/+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 1327801] Re: Bightness and contrast settings have no effect
And someone has that problem here: https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=920216 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1327801 Title: Bightness and contrast settings have no effect Status in simple-scan package in Ubuntu: Triaged Bug description: Scanner: Canon, Inc. CanoScan N1240U/LiDE 30 Ubuntu 14.04, Simple Scan version 3.12.1. Adjusting the settings of brightness and contrast has no effect. With the default for scanning in "text" mode being too bright, this makes "Simple Scan" in text mode unusable for me. Brightness and contrast settings don't work in "foto" mode, too. But the default of the foto mode is usable. Brightness setting does work in program "Skanlite". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1327801/+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 1327801] Re: Bightness and contrast settings have no effect
Same here. Canon MX395, Ubuntu Bionic, Sane over network, Simple Scan: 3.28.0 and 3.32.0 - both no effect on those setting. Skanlite do work. ** Bug watch added: Debian Bug tracker #920216 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920216 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1327801 Title: Bightness and contrast settings have no effect Status in simple-scan package in Ubuntu: Triaged Bug description: Scanner: Canon, Inc. CanoScan N1240U/LiDE 30 Ubuntu 14.04, Simple Scan version 3.12.1. Adjusting the settings of brightness and contrast has no effect. With the default for scanning in "text" mode being too bright, this makes "Simple Scan" in text mode unusable for me. Brightness and contrast settings don't work in "foto" mode, too. But the default of the foto mode is usable. Brightness setting does work in program "Skanlite". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1327801/+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 have seen this on bionic, then on cosmic and now on disco. Type password and it takes 5 to 6 seconds to give you the desktop. -- 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: Incomplete Status in gnome-shell package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete 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 1837890] [NEW] nvidia-graphics-drivers-340 340.107-0ubuntu5 ADT test failure with linux 5.3.0-0.1
Public bug reported: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/amd64/n/nvidia-graphics-drivers-340/20190724_125459_e1488@/log.gz ** Affects: nvidia-graphics-drivers-340 (Ubuntu) Importance: Undecided Status: New ** Tags: kernel-adt-failure ** Tags added: kernel-adt-failure -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1837890 Title: nvidia-graphics-drivers-340 340.107-0ubuntu5 ADT test failure with linux 5.3.0-0.1 Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/amd64/n/nvidia-graphics-drivers-340/20190724_125459_e1488@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1837890/+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 780491] Re: (Wishlist) Please, add a keyboard shortcut to show/hide the toolbar
Bug report refers to the old interface which had a conventional toolbar. In the new interface the top bar auto-hides when in full screen mode. Closing as report is no longer valid. ** Changed in: evince (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/780491 Title: (Wishlist) Please, add a keyboard shortcut to show/hide the toolbar Status in evince package in Ubuntu: Invalid Bug description: Binary package hint: evince With my small-screen netbook, and after change to fullscreen (F11), I have not a mean to hide the toolbar without switching back to windowed mode. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: evince 2.32.0-0ubuntu12.1 ProcVersionSignature: Ubuntu 2.6.39-1.6-generic 2.6.39-rc6 Uname: Linux 2.6.39-1-generic i686 Architecture: i386 Date: Tue May 10 14:33:19 2011 EcryptfsInUse: Yes ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature_: Ubuntu 2.6.39-1.6-generic 2.6.39-rc6 SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/780491/+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 880952] Re: Evince prints gdk critical failings on console output
We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. This bug was reported some time ago and there have been many changes in Ubuntu since that time. Ubuntu 11.10 (oneiric) reached end-of-life on May 9, 2013. Does anyone still see a problem related to the one that was reported when using a currently supported version of Ubuntu? Please let us know if you do otherwise this report can be left to expire in approximately 60 days time. Thank you for helping make Ubuntu better. Paul White [Ubuntu Bug Squad] ** Changed in: evince (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/880952 Title: Evince prints gdk critical failings on console output Status in evince package in Ubuntu: Incomplete Bug description: Evince is printing a bunch of gdk critical warnings when running from the console to open any kind of pdf file. Example: $ evince template.pdf (evince:2750): GLib-GObject-WARNING **: g_object_set_valist: construct property "enable-gestures" for object `EvView' can't be set after construction (evince:2750): Gdk-CRITICAL **: gdk_window_get_pointer: assertion `GDK_IS_WINDOW (window)' failed ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: evince 3.2.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic-pae 3.0.4 Uname: Linux 3.0.0-12-generic-pae i686 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu3 Architecture: i386 Date: Mon Oct 24 14:17:51 2011 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012) ProcEnviron: PATH=(custom, no user) LANG=en_US.ISO-8859-1 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/880952/+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 1837437] Re: disk content permanently lost when changing LUKS password
Attaching a debdiff for a disco SRU, as I don't have upload permission for
libblockdev.
Please sponsor!
** Patch added: "debdiff 2.20-7 -> 2.20-7ubuntu0.1"
https://bugs.launchpad.net/ubuntu/+source/libblockdev/+bug/1837437/+attachment/5279177/+files/libblockdev.debdiff
** Description changed:
- This is fixed upstream. Logging this bug to track the fix in to Ubuntu.
+ [Impact]
+ Users with full disk encryption trying to change the encryption
+ passphrase in gnome-disks will get an error message, and after rebooting
+ neither the old passphrase nor the new one can unlock their disk,
+ rendering the machine unusable.
+
+
+ [Test Case]
+
+ (can be done in a virtual machine, for testing purposes)
+ 1. Download a 19.04 ISO, and install it, choosing the full disk encryption
option
+ 2. When rebooting after the installation is complete, you are prompted for
your passphrase to unlock the disk
+ 3. Once logged in, open gnome-disks, select the encrypted disk and click the
contextual action to change the encryption passphrase
+ 4. Enter your old passphrase and the new one (twice), as prompted, then click
OK
+
+ Expected result: the passphrase is changed successfully, and when
+ rebooting the new passphrase can unlock the disk
+
+ Current result: changing the passphrase fails, the user is presented
+ with an error message ("Error changing passphrase on device /dev/sda5:
+ Failed to add the new passphrase: Invalid argument (udisks-error-quark,
+ 0)"), and when rebooting neither the old passphrase nor the new one can
+ unlock the disk, which renders it unusable
+
+ To test the fix, the updated libblockdev* packages need to be installed
+ on the machine before attempting to change the encryption passphrase in
+ gnome-disks.
+
+
+ [Regression Potential]
+
+ The patch only touches code related to changing the LUKS encryption
passphrase, so non-encrypted disk setups should not be affected.
+ Scenarii with full-disk encryption should be carefully tested, including
changing an existing passphrase, adding and removing passphrases, both from the
gnome-disks UI and using the cryptsetup CLI.
+
+
+ [Original Description]
+
+ This is fixed upstream. Logging this bug to track the fix in to Ubuntu.
From the upstream bug:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928893
Dear Maintainer,
* What led up to the situation?
Install system using normal full disk encryption LUKS+Ext4.
After install open gnome-disk-utility and change
encryption password. It gives some error dialog and
now you are royally screwed. It deleted the only
LUKS keyslot. Cannot add new keyslots because of that.
All data will be lost after reboot.
Here is output of luksdump:
udo cryptsetup luksDump /dev/sda5
LUKS header information
- Version:2
- Epoch: 4
- Metadata area: 16384 [bytes]
- Keyslots area: 1678 [bytes]
- UUID: 3c16ad4c-294c-4547-bf3e-bb8864ba5ea3
- Label: (no label)
- Subsystem: (no subsystem)
- Flags: (no flags)
+ Version: 2
+ Epoch: 4
+ Metadata area: 16384 [bytes]
+ Keyslots area: 1678 [bytes]
+ UUID: 3c16ad4c-294c-4547-bf3e-bb8864ba5ea3
+ Label: (no label)
+ Subsystem: (no subsystem)
+ Flags: (no flags)
Data segments:
0: crypt
offset: 16777216 [bytes]
length: (whole device)
cipher: aes-xts-plain64
sector: 512 [bytes]
Keyslots:
Tokens:
Digests:
0: pbkdf2
- Hash: sha256
+ Hash: sha256
Iterations: 59904
- Salt: XX XX XX XX XX
- Digest: XX XX XX XX XX ...
+ Salt: XX XX XX XX XX
+ Digest: XX XX XX XX XX ...
I changed salt and digest. No Keyslots are present!!!
I tried this 2 times in a row with new install,
exactly same result.
-
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.0.8-xanmod5 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8),
LANGUAGE=ru_RU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages gnome-disk-utility depends on:
- ii dconf-gsettings-backend [gsettings-backend] 0.30.1-2
- ii libatk1.0-0 2.30.0-2
- ii libc62.28-10
- ii libcairo21.16.0-4
- ii libcanberra-gtk3-0 0.30-7
- ii libdvdread4 6.0.1-1
- ii libgdk-pixbuf2.0-0 2.38.1+dfsg-1
- ii libglib2.0-0 2.58.3-1
- ii libgtk-3-0 3.24.5-1
- ii liblzma5
[Desktop-packages] [Bug 1837834] Re: Add support for Linux 5.0-5.2
** Description changed: Backport the compatibility patches available in 19.10. + + SRU Request: + + [Impact] + Linux 5.0 is not supported by nvidia-driver-340 in bionic. + + [Test Case] + 1) Enable the -proposed repository, and install the new 340 NVIDIA driver (340.107-0ubuntu0.16.04.3). + + 2) Check that the kernel module can be built against the new kernel. + + 3) Restart your computer, and see if everything works correctly when + accessing the desktop. + + [Regression Potential] + Low. The update only fixes build issues with Linux versions 5.0 - 5.2. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1837834 Title: Add support for Linux 5.0-5.2 Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 source package in Bionic: In Progress Bug description: Backport the compatibility patches available in 19.10. SRU Request: [Impact] Linux 5.0 is not supported by nvidia-driver-340 in bionic. [Test Case] 1) Enable the -proposed repository, and install the new 340 NVIDIA driver (340.107-0ubuntu0.16.04.3). 2) Check that the kernel module can be built against the new kernel. 3) Restart your computer, and see if everything works correctly when accessing the desktop. [Regression Potential] Low. The update only fixes build issues with Linux versions 5.0 - 5.2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1837834/+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 1829838] Re: 1.10.14-0ubuntu2 breaks DNS propagation from VPN
My systemd is newer (237-3ubuntu10.24), instead network manager is locked at 1.10.6 (1.10.6-2ubuntu1.1). I've upgraded network-manager as suggested to 1.10.14-0ubuntu2 and rebooted. I've shut down both my Wifi and LAN since I'm at the office, and hooked up my phone with USB tethering to use an external connection and use the VPN to my office. First test: it works. I get my DNS from the VPN: Link 61 (tun2) Current Scopes: DNS LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 172.27.0.42 172.27.0.33 DNS Domain: ~. Following the test case in #1754671: when I enable the split connection, this is the full result of systemd-resolve --status, where I do not see any DNS coming from the VPN: Global DNS Domain: mycompany.com DNSSEC NTA: 10.in-addr.arpa 16.172.in-addr.arpa 168.192.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa corp d.f.ip6.arpa home internal intranet lan local private test Link 48 (tun1) Current Scopes: none LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no Link 43 (tun0) Current Scopes: none LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no Link 42 (enp0s20f0u2) Current Scopes: DNS LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 192.168.42.129 DNS Domain: ~. Link 11 (br-b2c3b7f9b208) Current Scopes: none LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no Link 10 (br-775248335fa8) Current Scopes: none LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no Link 9 (br-6671ba352ece) Current Scopes: none LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no Link 8 (br-642ed19f0ac7) Current Scopes: none LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no Link 7 (br-5699f03e12bc) Current Scopes: none LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no Link 6 (br-1f97d7363f0e) Current Scopes: none LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no Link 5 (docker0) Current Scopes: none LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no Link 4 (br-dbf7ef8f9ab9) Current Scopes: none LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no Link 3 (wlp2s0) Current Scopes: none LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no Link 2 (enx106530b07160) Current Scopes: none LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no -- 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/1829838 Title: 1.10.14-0ubuntu2 breaks DNS propagation from VPN Status in network-manager package in Ubuntu: Incomplete Bug description: I have an OpenVPN connection, and I use the update-systemd-resolved to correctly fetch the DNS from the VPN. The issue arose updating my Ubuntu 18.04: the script is no longer invoked, and even invoking it manually (sudo openvpn myfile.ovpn) does not work anymore, even if in that case systemd-resolve --status shows the new DNS on the interface correctly. As suggested in https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/120/comments/99, reverting to 1.10.6-2ubuntu1.1 fixes the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829838/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe :
[Desktop-packages] [Bug 1837827] Re: nvidia-340 340.107-0ubuntu0.16.04.2: nvidia kernel module failed to build
Are there other drivers listed at: ubuntu-drivers list? if yes, try a 390 on that card -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1837827 Title: nvidia-340 340.107-0ubuntu0.16.04.2: nvidia kernel module failed to build Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: nvidia-340 340.107-0ubuntu0.16.04.2: nvidia kernel module failed to build ProblemType: Package DistroRelease: Ubuntu 16.04 Package: nvidia-340 340.107-0ubuntu0.16.04.2 ProcVersionSignature: Ubuntu 4.4.0-154.181-generic 4.4.179 Uname: Linux 4.4.0-154-generic x86_64 NonfreeKernelModules: nvidia_uvm 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.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.107 Thu May 24 21:54:01 PDT 2018 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.11) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None DKMSKernelVersion: 4.4.0-157-generic Date: Wed Jul 24 22:46:10 2019 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GT216 [GeForce GT 220] [10de:0a20] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GT216 [GeForce GT 220] [1462:1910] InstallationDate: Installed on 2015-11-14 (1348 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: HP-Pavilion AY600AA-ABA HPE-127c PackageVersion: 340.107-0ubuntu0.16.04.2 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-154-generic root=UUID=55fcadff-651e-d101-002c-a5ff651ed101 ro quiet splash nomodeset usbcore.autosuspend=-1 RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.32 SourcePackage: nvidia-graphics-drivers-340 Title: nvidia-340 340.107-0ubuntu0.16.04.2: nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.07 dmi.board.name: IONA dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.07:bd12/21/2009:svnHP-Pavilion:pnAY600AA-ABAHPE-127c:pvr:rvnMSI:rnIONA:rvr1.0:cvnHewlett-Packard:ct3:cvr: dmi.product.name: AY600AA-ABA HPE-127c dmi.sys.vendor: HP-Pavilion modified.conffile..etc.modprobe.d.nvidia-340_hybrid.conf: [deleted] version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Wed Jul 24 21:47:47 2019 xserver.configfile: default xserver.errors: open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1837827/+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 644517] Re: package flashplugin-installer 10.1.85.3ubuntu0.9.10.1 failed to install/upgrade: sub-processo script post-installation instalado foi morto por sinal (Interrupção)
** Changed in: flashplugin-nonfree (Ubuntu) Assignee: (unassigned) => wachirapranee tesprasit (tatar28) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to flashplugin-nonfree in Ubuntu. https://bugs.launchpad.net/bugs/644517 Title: package flashplugin-installer 10.1.85.3ubuntu0.9.10.1 failed to install/upgrade: sub-processo script post-installation instalado foi morto por sinal (Interrupção) Status in flashplugin-nonfree package in Ubuntu: New Bug description: Binary package hint: flashplugin-nonfree not conect site from download ProblemType: Package AptOrdering: flashplugin-installer: Install flashplugin-installer: Configure Architecture: amd64 Date: Tue Sep 21 10:50:35 2010 DistroRelease: Ubuntu 9.10 ErrorMessage: sub-processo script post-installation instalado foi morto por sinal (Interrupção) InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) NonfreeKernelModules: nvidia Package: flashplugin-installer 10.1.85.3ubuntu0.9.10.1 ProcVersionSignature: Ubuntu 2.6.31-22.65-generic SourcePackage: flashplugin-nonfree Title: package flashplugin-installer 10.1.85.3ubuntu0.9.10.1 failed to install/upgrade: sub-processo script post-installation instalado foi morto por sinal (Interrupção) Uname: Linux 2.6.31-22-generic x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flashplugin-nonfree/+bug/644517/+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 526948] Re: package flashplugin-nonfree 10.0.1.218+really9.0.262.0ubuntu1 failed to install/upgrade: El paquete está en un estado muy malo e inconsistente - debe reinstalarlo
*** This bug is a duplicate of bug 429841 *** https://bugs.launchpad.net/bugs/429841 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: flashplugin-nonfree (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to flashplugin-nonfree in Ubuntu. https://bugs.launchpad.net/bugs/526948 Title: package flashplugin-nonfree 10.0.1.218+really9.0.262.0ubuntu1 failed to install/upgrade: El paquete está en un estado muy malo e inconsistente - debe reinstalarlo antes de intentar desinstalarlo. Status in flashplugin-nonfree package in Ubuntu: Confirmed Bug description: Binary package hint: flashplugin-nonfree package flashplugin-nonfree 10.0.1.218+really9.0.262.0ubuntu1 failed to install/upgrade: El paquete está en un estado muy malo e inconsistente - debe reinstalarlo antes de intentar desinstalarlo. ProblemType: Package AptOrdering: flashplugin-nonfree: Remove flashplugin-installer: Install flashplugin-nonfree: Install flashplugin-installer: Configure flashplugin-nonfree: Configure Architecture: i386 Date: Wed Feb 24 10:58:59 2010 DistroRelease: Ubuntu 9.10 ErrorMessage: El paquete está en un estado muy malo e inconsistente - debe reinstalarlo antes de intentar desinstalarlo. LiveMediaBuild: Ubuntu 8.04.1 "Hardy Heron" - Release i386 (20080702.1) Package: flashplugin-nonfree 10.0.1.218+really9.0.262.0ubuntu1 ProcVersionSignature: Ubuntu 2.6.31-19.56-generic SourcePackage: flashplugin-nonfree Title: package flashplugin-nonfree 10.0.1.218+really9.0.262.0ubuntu1 failed to install/upgrade: El paquete está en un estado muy malo e inconsistente - debe reinstalarlo antes de intentar desinstalarlo. Uname: Linux 2.6.31-19-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flashplugin-nonfree/+bug/526948/+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
