[Bug 2069480] [NEW] nvidia-dkms-535 535.154.05-N~3~ubuntu24.04.1: nvidia kernel module failed to build
Public bug reported: Can't update Nvidia card ProblemType: Package DistroRelease: Ubuntu 24.04 Package: nvidia-dkms-535 535.154.05-N~3~ubuntu24.04.1 ProcVersionSignature: Ubuntu 6.8.0-35.35-generic 6.8.4 Uname: Linux 6.8.0-35-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass DKMSKernelVersion: 6.8.0-35-generic Date: Fri Jun 14 18:54:13 2024 InstallationDate: Installed on 2024-05-02 (43 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) PackageVersion: 535.154.05-N~3~ubuntu24.04.1 Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 3.12.3-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.22.6ubuntu6 apt 2.7.14build2 SourcePackage: nvidia-graphics-drivers-535 Title: nvidia-dkms-535 535.154.05-N~3~ubuntu24.04.1: nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-535 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package noble third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069480 Title: nvidia-dkms-535 535.154.05-N~3~ubuntu24.04.1: nvidia kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535/+bug/2069480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1376380] Re: lxsession risks filling disk with improper log handling
It filled all my disk, when I checked it was about 50gb! I used the following hack to fix the problem for now, removed the write permission for all users chmod a= ~/.cache/lxsession/Lubuntu/run.log ls -lha ~/.cache/lxsession/Lubuntu/run.log -- 1 typer typer 17K nov 23 21:47 /home/typer/.cache/lxsession/Lubuntu/run.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1376380 Title: lxsession risks filling disk with improper log handling To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxsession/+bug/1376380/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890791]
Sounds like a broken inotify. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890791 Title: Dolphin isn't Noticing Newly Created Files To manage notifications about this bug go to: https://bugs.launchpad.net/dolphin/+bug/1890791/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1791427] Re: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th
Anyone know what happened to Aaron's patch? The discussion at https://patchwork.kernel.org/patch/10822515/ ends on November last year with this question from Kai-Heng: > Users reported that patch [1/2] alone can solve the issue. > > Do we need more information before making this fix merged? > > Kai-Heng Would be really great if it could be merged :( Anyone tried a very recent kernel and can confirm the issue is still there BTW? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1791427 Title: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791427/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1885010] Re: NULL deference in nfs4_get_valid_delegation
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1885010 Title: NULL deference in nfs4_get_valid_delegation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885010/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1885010] Re: NULL deference in nfs4_get_valid_delegation
The test on 5.4.0-40.44 from focal-proposed was successful, so I would say that the fix did it. Thanks for including it! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1885010 Title: NULL deference in nfs4_get_valid_delegation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885010/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1885010] Re: NULL deference in nfs4_get_valid_delegation
The long production job with the custom built kernel finished successfully. I'm very confident this fixes our issue. Now running with 5.4.0-40.44 from focal-proposed as a test. I'll let it run for a few hours. It usually hits the crash in an hour or so. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1885010 Title: NULL deference in nfs4_get_valid_delegation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885010/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1885010] Re: NULL deference in nfs4_get_valid_delegation
Ah, I would really like to get this job that is running done first. It's processing some data we need to ideally should deliver on Monday. It's looking good so far, so I'm quite confident the fix is good. When it's done processing, I can give 5.4.0-40 from proposed a try and restart the job again. But I'm pretty sure that it's going to be good. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1885010 Title: NULL deference in nfs4_get_valid_delegation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885010/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1885010] Re: NULL deference in nfs4_get_valid_delegation
No worries Guilherme, that explains it. I've now built my own kernel from the Ubuntu-5.4.0-38.42 Git tag, which I've verified includes the fix. I'm running our workload again with this kernel and will know within a few hours whether it's looking good. The job as a whole is going to take the full weekend to finish. If it works fine, we can run on this custom kernel until 5.4.0-40 is out around next week. I'm both testing, but also trying to get actual work done here (get our job run to run to completion). Your fast support here was much appreciated. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1885010 Title: NULL deference in nfs4_get_valid_delegation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885010/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1885010] Re: NULL deference in nfs4_get_valid_delegation
Hi Matthew, thanks a lot for looking into this. Like you, I looked at Git to double-check, and thought the fix was in there, but it was next on my list to actually double-double-check, since I thought it so strange the issue wasn't gone. Thanks for offering to build a test kernel! I will have a go at it myself right away. I was actually on my way to doing that before, but got a silly error at the end of the build because I had been sloppy with installing the build depends and was missing gawk (so some final step failed where gawk was used in the build machinery). But just as I got to that error, I was informed that the fix was probably in 5.4.0-39 and canceled my building efforts. I'll report back how it goes. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1885010 Title: NULL deference in nfs4_get_valid_delegation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885010/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1885010] Re: NULL deference in nfs4_get_valid_delegation
I'm sad to say, but it seems it did not fix our problem. The crash happened again after running for about an hour: [ 4914.661585] BUG: unable to handle page fault for address: ffb0 [ 4914.661620] #PF: supervisor read access in kernel mode [ 4914.661638] #PF: error_code(0x) - not-present page [ 4914.661656] PGD 1b6580e067 P4D 1b6580e067 PUD 1b65810067 PMD 0 [ 4914.661680] Oops: [#1] SMP NOPTI [ 4914.661695] CPU: 12 PID: 4840 Comm: kworker/u130:5 Tainted: P OE 5.4.0-39-generic #43-Ubuntu [ 4914.661725] Hardware name: GIGABYTE G291-Z20-00/MZ21-G20-00, BIOS F06 10/04/2019 [ 4914.661770] Workqueue: rpciod rpc_async_schedule [sunrpc] [ 4914.661803] RIP: 0010:nfs4_get_valid_delegation+0xd/0x30 [nfsv4] [ 4914.661824] Code: 89 ef e8 76 0f ce ff e9 ec fd ff ff 90 0f 1f 44 00 00 55 48 89 e5 f0 80 4f 48 08 5d c3 0f 1f 44 00 00 55 31 f6 48 89 e5 41 54 <4c> 8b 67 b0 4c 89 e7 e8 07 f9 ff ff 84 c0 b8 00 00 00 00 4c 0f 44 [ 4914.661879] RSP: 0018:a0c1e0193d98 EFLAGS: 00010246 [ 4914.661898] RAX: 8b35bd8400c0 RBX: 8b3dc849f000 RCX: [ 4914.661920] RDX: 8000 RSI: RDI: [ 4914.661942] RBP: a0c1e0193da0 R08: R09: 8080808080808080 [ 4914.661965] R10: 8b3da8b397ac R11: 0018 R12: 8b3d93417300 [ 4914.661988] R13: R14: 8b45ccf6e000 R15: c0696950 [ 4914.662011] FS: () GS:8b3dcf90() knlGS: [ 4914.662036] CS: 0010 DS: ES: CR0: 80050033 [ 4914.662056] CR2: ffb0 CR3: 0007df20e000 CR4: 003406e0 [ 4914.662078] Call Trace: [ 4914.662101] nfs4_open_prepare+0x89/0x1e0 [nfsv4] [ 4914.662128] rpc_prepare_task+0x1f/0x30 [sunrpc] [ 4914.662154] __rpc_execute+0x8c/0x3a0 [sunrpc] [ 4914.662179] rpc_async_schedule+0x30/0x50 [sunrpc] [ 4914.662199] process_one_work+0x1eb/0x3b0 [ 4914.662215] worker_thread+0x4d/0x400 [ 4914.662230] kthread+0x104/0x140 [ 4914.662244] ? process_one_work+0x3b0/0x3b0 [ 4914.662259] ? kthread_park+0x90/0x90 [ 4914.662275] ret_from_fork+0x1f/0x40 [ 4914.662290] Modules linked in: rpcsec_gss_krb5 auth_rpcgss md4 cmac nfsv4 nls_utf8 cifs nfs libarc4 lockd grace libdes fscache aufs overlay ipmi_ssif binfmt_misc snd_hda_codec_hdmi amd64_edac_mod edac_mce_amd kvm_amd nls_iso8859_1 kvm snd_hda_intel snd_intel_dspcfg snd_hda_codec snd_hda_core snd_hwdep snd_pcm snd_seq_midi ucsi_ccg snd_seq_midi_event typec_ucsi typec snd_rawmidi snd_seq snd_seq_device snd_timer snd soundcore k10temp ccp ipmi_si mac_hid nvidia_uvm(OE) sch_fq_codel parport_pc ppdev lp parport sunrpc ip_tables x_tables autofs4 mlx5_ib nvidia_drm(POE) nvidia_modeset(POE) ib_uverbs ib_core nvidia(POE) crct10dif_pclmul crc32_pclmul ghash_clmulni_intel ast drm_vram_helper i2c_algo_bit ttm aesni_intel mlx5_core drm_kms_helper ixgbe syscopyarea crypto_simd sysfillrect nvme sysimgblt fb_sys_fops pci_hyperv_intf cryptd xfrm_algo dca glue_helper mdio drm tls nvme_core ahci mlxfw libahci ipmi_devintf i2c_piix4 ipmi_msghandler i2c_nvidia_gpu [ 4914.662566] CR2: ffb0 [ 4914.662581] ---[ end trace cdb67bb8c51af6b1 ]--- [ 4914.662608] RIP: 0010:nfs4_get_valid_delegation+0xd/0x30 [nfsv4] [ 4914.663407] Code: 89 ef e8 76 0f ce ff e9 ec fd ff ff 90 0f 1f 44 00 00 55 48 89 e5 f0 80 4f 48 08 5d c3 0f 1f 44 00 00 55 31 f6 48 89 e5 41 54 <4c> 8b 67 b0 4c 89 e7 e8 07 f9 ff ff 84 c0 b8 00 00 00 00 4c 0f 44 [ 4914.665002] RSP: 0018:a0c1e0193d98 EFLAGS: 00010246 [ 4914.665836] RAX: 8b35bd8400c0 RBX: 8b3dc849f000 RCX: [ 4914.46] RDX: 8000 RSI: RDI: [ 4914.667858] RBP: a0c1e0193da0 R08: R09: 8080808080808080 [ 4914.669136] R10: 8b3da8b397ac R11: 0018 R12: 8b3d93417300 [ 4914.670414] R13: R14: 8b45ccf6e000 R15: c0696950 [ 4914.671692] FS: () GS:8b3dcf90() knlGS: [ 4914.672980] CS: 0010 DS: ES: CR0: 80050033 [ 4914.674267] CR2: ffb0 CR3: 0007df20e000 CR4: 003406e0 This was with (env) orexplore@sleipner:~$ uname -a Linux sleipner 5.4.0-39-generic #43-Ubuntu SMP Fri Jun 19 10:28:31 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux (env) orexplore@sleipner:~$ from linux-image-5.4.0-39-generic 5.4.0-39.43 in focal-proposed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1885010 Title: NULL deference in nfs4_get_valid_delegation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885010/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1885010] Re: NULL deference in nfs4_get_valid_delegation
Thanks Guilherme, shame on me for not even checking that :) I will try with 5.4.0-39 and report back. It takes a while for our workload to run before it starts hitting the issue, but I can give a somewhat confident answer in an hour or so. By tomorrow I will be very sure. I'm optimistic. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1885010 Title: NULL deference in nfs4_get_valid_delegation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885010/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1885010] [NEW] NULL deference in nfs4_get_valid_delegation
Public bug reported: We are getting the following on an NFSv4 client running focal (kernel 5.4.0-33.37): [296787.347971] BUG: unable to handle page fault for address: ffb0 [296787.350255] #PF: supervisor read access in kernel mode [296787.352315] #PF: error_code(0x) - not-present page [296787.354137] PGD 15bf00e067 P4D 15bf00e067 PUD 15bf010067 PMD 0 [296787.355798] Oops: [#2] SMP NOPTI [296787.357271] CPU: 49 PID: 605315 Comm: kworker/u131:3 Tainted: P D OE 5.4.0-33-generic #37-Ubuntu [296787.358756] Hardware name: GIGABYTE G291-Z20-00/MZ21-G20-00, BIOS F06 10/04/2019 [296787.360274] Workqueue: rpciod rpc_async_schedule [sunrpc] [296787.361790] RIP: 0010:nfs4_get_valid_delegation+0xd/0x30 [nfsv4] [296787.363281] Code: 89 ef e8 06 c0 f9 ff e9 ec fd ff ff 90 0f 1f 44 00 00 55 48 89 e5 f0 80 4f 48 08 5d c3 0f 1f 44 00 00 55 31 f6 48 89 e5 41 54 <4c> 8b 67 b0 4c 89 e7 e8 07 f9 ff ff 84 c0 b8 00 00 00 00 4c 0f 44 [296787.366780] RSP: 0018:b7b1634a7d98 EFLAGS: 00010246 [296787.368740] RAX: 9ef2958e9b00 RBX: 9ef59f91 RCX: [296787.370648] RDX: 8000 RSI: RDI: [296787.372559] RBP: b7b1634a7da0 R08: R09: 8080808080808080 [296787.374441] R10: 9ef731e9d26c R11: 0018 R12: 9ef781f22600 [296787.376330] R13: R14: 9efe1db4bc00 R15: c0cc2950 [296787.378220] FS: () GS:9ef78fc4() knlGS: [296787.380165] CS: 0010 DS: ES: CR0: 80050033 [296787.382076] CR2: ffb0 CR3: 001a2799c000 CR4: 003406e0 [296787.384031] Call Trace: [296787.385985] nfs4_open_prepare+0x89/0x1e0 [nfsv4] [296787.387973] rpc_prepare_task+0x1f/0x30 [sunrpc] [296787.389971] __rpc_execute+0x8c/0x3a0 [sunrpc] [296787.391903] rpc_async_schedule+0x30/0x50 [sunrpc] [296787.393787] process_one_work+0x1eb/0x3b0 [296787.395617] worker_thread+0x4d/0x400 [296787.397431] kthread+0x104/0x140 [296787.399166] ? process_one_work+0x3b0/0x3b0 [296787.400868] ? kthread_park+0x90/0x90 [296787.402518] ret_from_fork+0x1f/0x40 [296787.404158] Modules linked in: rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace sunrpc xt_nat xt_tcpudp veth xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c bpfilter br_netfilter bridge stp llc aufs overlay md4 cmac nls_utf8 cifs libarc4 fscache libdes binfmt_misc snd_hda_codec_hdmi amd64_edac_mod edac_mce_amd ipmi_ssif nls_iso8859_1 kvm_amd kvm snd_hda_intel snd_intel_dspcfg snd_hda_codec snd_seq_midi snd_seq_midi_event snd_hda_core snd_rawmidi snd_hwdep snd_pcm snd_seq snd_seq_device snd_timer ucsi_ccg snd typec_ucsi typec soundcore k10temp ccp ipmi_si mac_hid nvidia_uvm(OE) sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 mlx5_ib nvidia_drm(POE) nvidia_modeset(POE) ib_uverbs ib_core nvidia(POE) crct10dif_pclmul crc32_pclmul ghash_clmulni_intel ast drm_vram_helper aesni_intel i2c_algo_bit crypto_simd ixgbe cryptd ttm glue_helper xfrm_algo [296787.404232] drm_kms_helper mlx5_core dca mdio syscopyarea sysfillrect sysimgblt fb_sys_fops nvme pci_hyperv_intf drm tls nvme_core mlxfw ahci ipmi_devintf i2c_piix4 libahci ipmi_msghandler i2c_nvidia_gpu [296787.421858] CR2: ffb0 [296787.423680] ---[ end trace 2cf3edda87955a36 ]--- [296787.425547] RIP: 0010:nfs4_get_valid_delegation+0xd/0x30 [nfsv4] [296787.427389] Code: 89 ef e8 06 c0 f9 ff e9 ec fd ff ff 90 0f 1f 44 00 00 55 48 89 e5 f0 80 4f 48 08 5d c3 0f 1f 44 00 00 55 31 f6 48 89 e5 41 54 <4c> 8b 67 b0 4c 89 e7 e8 07 f9 ff ff 84 c0 b8 00 00 00 00 4c 0f 44 [296787.431172] RSP: 0018:b7b1615e3d98 EFLAGS: 00010246 [296787.433050] RAX: 9ee9faf45ec0 RBX: 9ef16c5dd000 RCX: [296787.434922] RDX: 8000 RSI: RDI: [296787.436810] RBP: b7b1615e3da0 R08: R09: 8080808080808080 [296787.438673] R10: 9ef26a0b8c6c R11: 0018 R12: 9ef7817cfa00 [296787.440539] R13: 0004 R14: 9ef8bdeb0400 R15: c0cc2950 [296787.442400] FS: () GS:9ef78fc4() knlGS: [296787.444289] CS: 0010 DS: ES: CR0: 80050033 [296787.446126] CR2: ffb0 CR3: 001a2799c000 CR4: 003406e0 The problem is a known issue which has been fixed upstream: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=29fe839976266bc7c55b927360a1daae57477723 The patch is a simple 2 line fix. Would be great if you could do an SRU and add that upstream patch. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.
[Bug 1878431] Re: [81C4, Realtek ALC298, Speaker, Internal] Playback problem
I saw in another bug that it would help if I ran RtHDDump.exe from windows 10. So I have and that should be attached next. The sounds in windows 10 is _great_. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878431 Title: [81C4, Realtek ALC298, Speaker, Internal] Playback problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1878431/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878431] Re: [81C4, Realtek ALC298, Speaker, Internal] Playback problem
** Attachment added: "Output from RtHDDump.exe" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1878431/+attachment/5370974/+files/RtHDDump.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878431 Title: [81C4, Realtek ALC298, Speaker, Internal] Playback problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1878431/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878431] Re: [81C4, Realtek ALC298, Speaker, Internal] Playback problem
** Attachment added: "python generated by hda-analyzer which makes things sound ok" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1878431/+attachment/5370972/+files/fixsound -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878431 Title: [81C4, Realtek ALC298, Speaker, Internal] Playback problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1878431/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878431] Re: [81C4, Realtek ALC298, Speaker, Internal] Playback problem
Played around with hda-analyzer and managed to get half decent sound. I've added the python code it generated. But I don't know how to configure things so that the volume keys adjust it. Attachment of the python should be below. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878431 Title: [81C4, Realtek ALC298, Speaker, Internal] Playback problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1878431/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878431] [NEW] [81C4, Realtek ALC298, Speaker, Internal] Playback problem
Public bug reported: I get thin tinny sound. On ubuntu 19.10 I was able to work around this by running: sudo hda-verb /dev/snd/hwC0D0 0x14 SET_CONNECT_SEL 0x0c But that doesn't seem to work on 20.04 and I haven't been able to work out what I need to do to get sound working acceptably. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: travis36906 F pulseaudio travis207783 F alsamixer CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 14 00:58:56 2020 InstallationDate: Installed on 2020-05-09 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_Type: None of the above Title: [81C4, Realtek ALC298, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/09/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 8GCN32WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA C930-13IKB dmi.modalias: dmi:bvnLENOVO:bvr8GCN32WW:bd10/09/2018:svnLENOVO:pn81C4:pvrLenovoYOGAC930-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct31:cvrLenovoYOGAC930-13IKB: dmi.product.family: YOGA C930-13IKB dmi.product.name: 81C4 dmi.product.sku: LENOVO_MT_81C4_BU_idea_FM_YOGA C930-13IKB dmi.product.version: Lenovo YOGA C930-13IKB dmi.sys.vendor: LENOVO ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878431 Title: [81C4, Realtek ALC298, Speaker, Internal] Playback problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1878431/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856024] Re: [SRU] Need backport-iwlwifi-dkms in Bionic
Alright, thanks Yang, makes sense. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856024 Title: [SRU] Need backport-iwlwifi-dkms in Bionic To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1856024/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856024] Re: [SRU] Need backport-iwlwifi-dkms in Bionic
Hi folks. I'm on bionic and got a desktop notification about "closed drivers may be necessary..." when this SRU landed in bionic-updates. Just to check: I only really need this package if I'm suffering from https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi- dkms/+bug/1859472 ? If I don't really have any issues with wifi, I can ignore the `backport-iwlwifi-dkms` package and use the `iwlwifi` driver that I already have from `linux-modules-extra-5.0.0-37-generic`? Or is it recommended for everyone to install this package? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856024 Title: [SRU] Need backport-iwlwifi-dkms in Bionic To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1856024/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856024] Re: [SRU] Need backport-iwlwifi-dkms in Bionic
(Forgot to say in my previous post, I'm using the HWE kernel, so 5.0.0-37 currently) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856024 Title: [SRU] Need backport-iwlwifi-dkms in Bionic To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1856024/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1833013] Re: Interactive prompt during non-interactive install
Robie: Nevermind, I was not setting up the env vars correctly. Sorry for the noise. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1833013 Title: Interactive prompt during non-interactive install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ansible/+bug/1833013/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1833013] Re: Interactive prompt during non-interactive install
Robie: We had one of our automated builds start failing due to this. We were using only -y and DEBIAN_FRONTEND=noninteractive (wrongly thinking that was enough). I've now changed to sudo apt-get -o Dpkg::Options::="--force-confdef" -o Dpkg::Options ::="--force-confold" -y install $(cat requirements-ubuntu.txt) and with DEBCONF_NONINTERACTIVE_SEEN=true, DEBIAN_FRONTEND=noninteractive and UCF_FORCE_CONFOLD=1 in the environment. But the prompt when configuring libssl1.1 still shows up, so the job hangs :( -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1833013 Title: Interactive prompt during non-interactive install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ansible/+bug/1833013/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1215182] Re: xfce 4 session manager does not save session
I am running Xubuntu 18.04.2 as well. This is relegated to a: I won't work, and you can't make me. Is there any solution to this? Please re-open this bug. It still exists after 6 years. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1215182 Title: xfce 4 session manager does not save session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-session/+bug/1215182/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813471]
(In reply to Wayne Mery (:wsmwk) from comment #8) > (In reply to Elvis Angelaccio from comment #3) > > Thanks for the link, it doesn't crash using that package. I'll report the > > crash downstream. > > Do you have a link? Sure: https://bugs.archlinux.org/task/61134 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813471 Title: Thunderbird crashes with GTK_USE_PORTAL environment variable. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1813471/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 361868]
*** Bug 194982 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/361868 Title: eject & reinsert of device does not reuse Dolphin instance To manage notifications about this bug go to: https://bugs.launchpad.net/kde-baseapps/+bug/361868/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809556] Re: zram freezes computer
I think the above link will not gonna help because it's related to computer freezing when RAM is full, my computer wasn't with high usage of RAM on the freeze moment, it was using something about 50% Another point is that zram makes computer use less RAM and my problem gone when I uninstalled zram, so the issue definitely is not related to high memory usage -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1809556 Title: zram freezes computer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zram-config/+bug/1809556/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 489952] Re: system freeze during shutdown - deactivating swap...
Format the Linux swap partition using gparted and update the new swap partition UUID on /etc/fstab did the trick for me -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/489952 Title: system freeze during shutdown - deactivating swap... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/489952/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809556] Re: zram freezes computer
** Description changed: I bought a new setup and since then my computer is having random - freezes, it stop respond until you make a hard reset (pressing reset - button) + freezes, the machine stops respond until you do a hard reset (pressing + reset button) * I noticed that this issue is more common when running java programs, i.e. Intellij, Spring Boot applications (I'm a java developer) and using chrome. * I also noticed issue is not related to high CPU usage Steps I did to reproduce the issues * Turned computer on * Started Intellij * Opened chrome and let a video playing * Started a java application with a considerable consume of memory (500MB) * Keep starting and stopping that application I did the following tests and had the same results * Tested on ubuntu 16.04, 18.04, 18.10 with it's original kernels, also tested on kernel 4.19 * Tested with nouveau (With and without GPU installed) * Tested with Nvidia proprietary drivers * Tested with Nvidia ubuntu repository drivers * Installed latest BIOs * Removed one of my two memories Steps I did to stress my computer and got no issues * Ran memtest (got no issues) * Stressed my computer and RAM with stress tool (got not issues) Steps to fix the problem * apt purge -y zram-config * Restart the computer -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1809556 Title: zram freezes computer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zram-config/+bug/1809556/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809556] Re: zram freezes computer
As the computer crashes I got no errors on the syslog except one time when I got the error attached on crash.txt ** Attachment added: "crash.txt" https://bugs.launchpad.net/ubuntu/+source/zram-config/+bug/1809556/+attachment/5224388/+files/crash.txt ** Description changed: I bought a new setup and since then my computer is having random freezes, it stop respond until you make a hard reset (pressing reset button) * I noticed that this issue is more common when running java programs, i.e. Intellij, Spring Boot applications (I'm a java developer) and using chrome. * I also noticed issue is not related to high CPU usage Steps I did to reproduce the issues * Turned computer on * Started Intellij * Opened chrome and let a video playing * Started a java application with a considerable consume of memory (500MB) * Keep starting and stopping that application I did the following tests and had the same results * Tested on ubuntu 16.04, 18.04, 18.10 with it's original kernels, also tested on kernel 4.19 * Tested with nouveau (With and without GPU installed) * Tested with Nvidia proprietary drivers * Tested with Nvidia ubuntu repository drivers * Installed latest BIOs * Removed one of my two memories Steps I did to stress my computer and got no issues * Ran memtest (got no issues) * Stressed my computer and RAM with stress tool (got not issues) Steps to fix the problem * apt purge -y zram-config * Restart the computer - - - **Update** - - As the computer crashes I got no errors on the syslog except one time - when I got the error attached on crash.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1809556 Title: zram freezes computer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zram-config/+bug/1809556/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809556] Re: zram freezes computer
https://launchpadlibrarian.net/402582096/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1809556 Title: zram freezes computer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zram-config/+bug/1809556/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809556] Re: zram freezes computer
https://launchpadlibrarian.net/402582127/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1809556 Title: zram freezes computer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zram-config/+bug/1809556/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809556] Re: zram freezes computer
ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: typer 2994 F pulseaudio /dev/snd/pcmC0D0p: typer 2994 F...m pulseaudio CurrentDesktop: LXQt DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-20 (2 days ago) InstallationMedia: Lubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 1c4f:0002 SiGma Micro Keyboard TRACER Gamma Ivory Bus 001 Device 002: ID 046d:c083 Logitech, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. B360M-D3H Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-12-generic root=UUID=ba2e86e4-48ce-47f3-a413-98536fe6febd ro quiet splash resume=UUID=5b571422-2d63-4044-88be-ecd5e66732d8 vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 RelatedPackageVersions: linux-restricted-modules-4.18.0-12-generic N/A linux-backports-modules-4.18.0-12-generic N/A linux-firmware 1.175.1 RfKill: Tags: cosmic Uname: Linux 4.18.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo _MarkForUpload: True dmi.bios.date: 04/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: Default string dmi.board.name: B360M D3H-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4:bd04/19/2018:svnGigabyteTechnologyCo.,Ltd.:pnB360M-D3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB360MD3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B360M-D3H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1809556 Title: zram freezes computer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zram-config/+bug/1809556/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809556] [NEW] zram freezes computer
Public bug reported: I bought a new setup and since then my computer is having random freezes, it stop respond until you make a hard reset (pressing reset button) * I noticed that this issue is more common when running java programs, i.e. Intellij, Spring Boot applications (I'm a java developer) and using chrome. * I also noticed issue is not related to high CPU usage Steps I did to reproduce the issues * Turned computer on * Started Intellij * Opened chrome and let a video playing * Started a java application with a considerable consume of memory (500MB) * Keep starting and stopping that application I did the following tests and had the same results * Tested on ubuntu 16.04, 18.04, 18.10 with it's original kernels, also tested on kernel 4.19 * Tested with nouveau (With and without GPU installed) * Tested with Nvidia proprietary drivers * Tested with Nvidia ubuntu repository drivers * Installed latest BIOs * Removed one of my two memories Steps I did to stress my computer and got no issues * Ran memtest (got no issues) * Stressed my computer and RAM with stress tool (got not issues) Steps to fix the problem * apt purge -y zram-config * Restart the computer ** Affects: zram-config (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1809556 Title: zram freezes computer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zram-config/+bug/1809556/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809556] Re: zram freezes computer
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1809556 Title: zram freezes computer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zram-config/+bug/1809556/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809556] Re: zram freezes computer
https://launchpadlibrarian.net/402582128/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1809556 Title: zram freezes computer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zram-config/+bug/1809556/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809556] Re: zram freezes computer
https://launchpadlibrarian.net/402582142/WifiSyslog.txt ** Description changed: I bought a new setup and since then my computer is having random freezes, it stop respond until you make a hard reset (pressing reset button) * I noticed that this issue is more common when running java programs, i.e. Intellij, Spring Boot applications (I'm a java developer) and using chrome. * I also noticed issue is not related to high CPU usage Steps I did to reproduce the issues * Turned computer on * Started Intellij * Opened chrome and let a video playing * Started a java application with a considerable consume of memory (500MB) * Keep starting and stopping that application I did the following tests and had the same results * Tested on ubuntu 16.04, 18.04, 18.10 with it's original kernels, also tested on kernel 4.19 * Tested with nouveau (With and without GPU installed) * Tested with Nvidia proprietary drivers * Tested with Nvidia ubuntu repository drivers * Installed latest BIOs * Removed one of my two memories Steps I did to stress my computer and got no issues * Ran memtest (got no issues) * Stressed my computer and RAM with stress tool (got not issues) - Steps to fix the problem - * apt purge -y zram-config + * apt purge -y zram-config * Restart the computer + + + **Update** + + As the computer crashes I got no errors on the syslog except one time + when I got the error attached on crash.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1809556 Title: zram freezes computer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zram-config/+bug/1809556/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809556] Re: zram freezes computer
https://launchpadlibrarian.net/402582121/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1809556 Title: zram freezes computer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zram-config/+bug/1809556/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1530405] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1530405/+attachment/5224262/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1530405 Title: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1530405/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1530405] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1530405/+attachment/5224260/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1530405 Title: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1530405/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1530405] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1530405/+attachment/5224253/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1530405 Title: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1530405/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1530405] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1530405/+attachment/5224258/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1530405 Title: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1530405/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1530405] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1530405/+attachment/5224251/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1530405 Title: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1530405/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1530405] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1530405/+attachment/5224261/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1530405 Title: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1530405/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1530405] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1530405/+attachment/5224257/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1530405 Title: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1530405/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1530405] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1530405/+attachment/5224259/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1530405 Title: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1530405/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1530405] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1530405/+attachment/5224250/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1530405 Title: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1530405/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1530405] Re: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814]
ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: typer 2994 F pulseaudio /dev/snd/pcmC0D0p: typer 2994 F...m pulseaudio CurrentDesktop: LXQt DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-20 (2 days ago) InstallationMedia: Lubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 1c4f:0002 SiGma Micro Keyboard TRACER Gamma Ivory Bus 001 Device 002: ID 046d:c083 Logitech, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. B360M-D3H Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-12-generic root=UUID=ba2e86e4-48ce-47f3-a413-98536fe6febd ro quiet splash resume=UUID=5b571422-2d63-4044-88be-ecd5e66732d8 vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 RelatedPackageVersions: linux-restricted-modules-4.18.0-12-generic N/A linux-backports-modules-4.18.0-12-generic N/A linux-firmware 1.175.1 RfKill: Tags: cosmic Uname: Linux 4.18.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo _MarkForUpload: True dmi.bios.date: 04/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: Default string dmi.board.name: B360M D3H-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4:bd04/19/2018:svnGigabyteTechnologyCo.,Ltd.:pnB360M-D3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB360MD3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B360M-D3H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Tags added: apport-collected cosmic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1530405 Title: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1530405/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1530405] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1530405/+attachment/5224256/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1530405 Title: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1530405/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1530405] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1530405/+attachment/5224254/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1530405 Title: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1530405/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1530405] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1530405/+attachment/5224252/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1530405 Title: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1530405/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1530405] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1530405/+attachment/5224255/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1530405 Title: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1530405/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1797538] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1797538/+attachment/5224245/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1797538 Title: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/0:1:85] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1797538] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1797538/+attachment/5224238/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1797538 Title: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/0:1:85] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1797538] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1797538/+attachment/5224247/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1797538 Title: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/0:1:85] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1797538] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1797538/+attachment/5224239/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1797538 Title: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/0:1:85] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1797538] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1797538/+attachment/5224242/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1797538 Title: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/0:1:85] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1797538] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1797538/+attachment/5224240/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1797538 Title: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/0:1:85] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1797538] Re: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/0:1:85]
ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: typer 2994 F pulseaudio /dev/snd/pcmC0D0p: typer 2994 F...m pulseaudio CurrentDesktop: LXQt DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-20 (2 days ago) InstallationMedia: Lubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 1c4f:0002 SiGma Micro Keyboard TRACER Gamma Ivory Bus 001 Device 002: ID 046d:c083 Logitech, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. B360M-D3H Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-12-generic root=UUID=ba2e86e4-48ce-47f3-a413-98536fe6febd ro quiet splash resume=UUID=5b571422-2d63-4044-88be-ecd5e66732d8 vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 RelatedPackageVersions: linux-restricted-modules-4.18.0-12-generic N/A linux-backports-modules-4.18.0-12-generic N/A linux-firmware 1.175.1 RfKill: Tags: cosmic Uname: Linux 4.18.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo _MarkForUpload: True dmi.bios.date: 04/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: Default string dmi.board.name: B360M D3H-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4:bd04/19/2018:svnGigabyteTechnologyCo.,Ltd.:pnB360M-D3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB360MD3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B360M-D3H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Tags added: apport-collected -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1797538 Title: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/0:1:85] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1797538] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1797538/+attachment/5224248/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1797538 Title: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/0:1:85] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1797538] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1797538/+attachment/5224241/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1797538 Title: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/0:1:85] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1797538] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1797538/+attachment/5224246/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1797538 Title: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/0:1:85] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1797538] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1797538/+attachment/5224249/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1797538 Title: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/0:1:85] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1797538] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1797538/+attachment/5224237/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1797538 Title: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/0:1:85] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1797538] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1797538/+attachment/5224244/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1797538 Title: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/0:1:85] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1797538] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1797538/+attachment/5224243/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1797538 Title: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/0:1:85] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1797538] Re: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/0:1:85]
For me the issue is happening on ubuntu 16.04, 18.04 and 18.10 I also tried kernel 4.19, no success -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1797538 Title: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/0:1:85] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 224436]
*** Bug 374717 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/224436 Title: Dolphin lacks open-as-root service menu To manage notifications about this bug go to: https://bugs.launchpad.net/kde-baseapps/+bug/224436/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 224436]
*** Bug 386057 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/224436 Title: Dolphin lacks open-as-root service menu To manage notifications about this bug go to: https://bugs.launchpad.net/kde-baseapps/+bug/224436/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 224436]
*** Bug 166708 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/224436 Title: Dolphin lacks open-as-root service menu To manage notifications about this bug go to: https://bugs.launchpad.net/kde-baseapps/+bug/224436/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 224436]
This is going to be a wontfix, since it's a report from early KDE4 times. Nowadays it's well established that running GUI apps as root is dangerous. Even more Dolphin, given that it comes with full shell access thanks to the embedded Konsole part. Anyone interested in editing root files with Dolphin, please subscribe to https://bugs.kde.org/show_bug.cgi?id=179678 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/224436 Title: Dolphin lacks open-as-root service menu To manage notifications about this bug go to: https://bugs.launchpad.net/kde-baseapps/+bug/224436/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 224436]
*** Bug 378169 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/224436 Title: Dolphin lacks open-as-root service menu To manage notifications about this bug go to: https://bugs.launchpad.net/kde-baseapps/+bug/224436/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 224436]
*** Bug 376336 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/224436 Title: Dolphin lacks open-as-root service menu To manage notifications about this bug go to: https://bugs.launchpad.net/kde-baseapps/+bug/224436/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 224436]
*** Bug 387950 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdebase in Ubuntu. https://bugs.launchpad.net/bugs/224436 Title: Dolphin lacks open-as-root service menu To manage notifications about this bug go to: https://bugs.launchpad.net/kde-baseapps/+bug/224436/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1799660] [NEW] CMake config file references files with wrong path
Public bug reported: I tried to use this package when building VTK from source, by passing the flag -Dpugixml_DIR=/usr/share/libpugixml-dev/cmake to the CMake configure step. This failed with CMake Error at /usr/share/libpugixml-dev/cmake/pugixml-config.cmake:87 (message): The imported target "pugixml" references the file "/lib/x86_64-linux-gnu/libpugixml.so.1.8" but this file does not exist. Possible reasons include: * The file was deleted, renamed, or moved to another location. * An install or uninstall procedure did not complete successfully. * The installation package was faulty and contained "/usr/share/libpugixml-dev/cmake/pugixml-config.cmake" but not all the files it references. Call Stack (most recent call first): CMake/vtkModuleMacros.cmake:891 (find_package) ThirdParty/pugixml/CMakeLists.txt:1 (vtk_module_third_party) Looking at /usr/share/libpugixml-dev/cmake/pugixml-config.cmake, this section of code: # Compute the installation prefix relative to this file. get_filename_component(_IMPORT_PREFIX "${CMAKE_CURRENT_LIST_FILE}" PATH) # Use original install prefix when loaded through a # cross-prefix symbolic link such as /lib -> /usr/lib. get_filename_component(_realCurr "${_IMPORT_PREFIX}" REALPATH) get_filename_component(_realOrig "/usr/lib/x86_64-linux-gnu/cmake/pugixml" REALPATH) if(_realCurr STREQUAL _realOrig) set(_IMPORT_PREFIX "/usr/lib/x86_64-linux-gnu/cmake/pugixml") endif() unset(_realOrig) unset(_realCurr) get_filename_component(_IMPORT_PREFIX "${_IMPORT_PREFIX}" PATH) get_filename_component(_IMPORT_PREFIX "${_IMPORT_PREFIX}" PATH) get_filename_component(_IMPORT_PREFIX "${_IMPORT_PREFIX}" PATH) get_filename_component(_IMPORT_PREFIX "${_IMPORT_PREFIX}" PATH) if(_IMPORT_PREFIX STREQUAL "/") set(_IMPORT_PREFIX "") endif() seems to arrive at a ${_IMPORT_PREFIX} of "", which means e.g. set_target_properties(pugixml PROPERTIES IMPORTED_LOCATION_NOCONFIG "${_IMPORT_PREFIX}/lib/x86_64-linux-gnu/libpugixml.so.1.8" IMPORTED_SONAME_NOCONFIG "libpugixml.so.1" ) in /usr/share/libpugixml-dev/cmake/pugixml-config-noconfig.cmake will become wrong ("/lib/x86_64-linux-gnu/libpugixml.so.1"), leading to config error. Looks like the calculation of ${_IMPORT_PREFIX} is wrong, not sure if this is because of some wrong assumption that doesn't hold. Seems to make it impossible to use this package from a CMake-using project (using -Dpugixml_DIR). ** Affects: pugixml (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799660 Title: CMake config file references files with wrong path To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pugixml/+bug/1799660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766366] Re: prime-select fails without grub
This is a problem for us as well. We're using Docker as part of our toolchain for creating a file system for a disk image for our product, and need to be able to run "prime-select intel" during the Docker image build, at a time when grub has not been installed yet. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766366 Title: prime-select fails without grub To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1766366/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769824] [NEW] Xorg crash
Public bug reported: System was idle at the time. It displayed the background wall paper, but did NOT display the login screen. I had to go to console, and restart lightdm. Wayno ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: XFCE Date: Mon May 7 23:16:23 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GT218 [GeForce 210] [3842:1312] InstallationDate: Installed on 2018-04-27 (10 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: HP-Pavilion KJ385AA-ABA a6433w ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=5c74d40b-8d0a-4abd-b32e-fca693b36f98 ro quiet splash SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/10/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.43 dmi.board.name: Benicia dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.01 dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.43:bd09/10/2009:svnHP-Pavilion:pnKJ385AA-ABAa6433w:pvr:rvnPEGATRONCORPORATION:rnBenicia:rvr1.01:cvnHewlett-Packard:ct3:cvrChassisVersion: dmi.product.family: 103C_53316J dmi.product.name: KJ385AA-ABA a6433w dmi.sys.vendor: HP-Pavilion version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic crash ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769824 Title: Xorg crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1769824/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1751497] Re: Bionic daily build - nouveau: Direct firmware load for nouveau/nve7_fuc084 failed with error -2
confirmed in xubuntu 18.04 Linux bart 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux [261304.111515] nouveau :04:00.0: Direct firmware load for nouveau/nva8_fuc084 failed with error -2 [261304.111529] nouveau :04:00.0: Direct firmware load for nouveau/nva8_fuc084d failed with error -2 [261304.111532] nouveau :04:00.0: msvld: unable to load firmware data [261304.111538] nouveau :04:00.0: msvld: init failed, -19 [340065.706109] perf: interrupt took too long (9727 > 9721), lowering kernel.perf_event_max_sample_rate to 20500 [348688.301567] nouveau :04:00.0: fb: trapped read at 01008bc04c on channel -1 [3fee unknown] engine 06 [BAR] client 08 [PFIFO_READ] subclient 01 [IN] reason 0002 [PAGE_NOT_PRESENT] [348698.597698] nouveau :04:00.0: Direct firmware load for nouveau/nva8_fuc084 failed with error -2 [348698.597714] nouveau :04:00.0: Direct firmware load for nouveau/nva8_fuc084d failed with error -2 [348698.597717] nouveau :04:00.0: msvld: unable to load firmware data [348698.597723] nouveau :04:00.0: msvld: init failed, -19 Elvis -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1751497 Title: Bionic daily build - nouveau: Direct firmware load for nouveau/nve7_fuc084 failed with error -2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1751497/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1755380] Re: [FFe] Please sync c-blosc 1.14.0+ds1-1 from debian unstable to bionic (1.11.1 has format incompat bug!)
@ginggs: Thanks for the heads up. I could reproduce the problem with bcolz from the Git master branch, and I've filed an upstream issue here: https://github.com/Blosc/bcolz/issues/374 (the upstream author for both packages are the same, so hopefully it's an easy fix). ** Bug watch added: github.com/Blosc/bcolz/issues #374 https://github.com/Blosc/bcolz/issues/374 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755380 Title: [FFe] Please sync c-blosc 1.14.0+ds1-1 from debian unstable to bionic (1.11.1 has format incompat bug!) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/c-blosc/+bug/1755380/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1755380] Re: [FFe] Please sync c-blosc 1.14.0+ds1-1 from debian unstable to bionic (1.11.1 has format incompat bug!)
I've now also tested 1.14.2+ds1-1 which finally landed in -proposed (the 1.14.0+ds1-1 build failed because of an alignment issue on ARM that was subsequently fixed). The package is looking good (transcript of testing below). root@f0b7772b23f5:/usr/share/doc/libblosc-dev/examples# apt-cache policy libblosc* libblosc-dev: Installed: 1.14.2+ds1-1 Candidate: 1.14.2+ds1-1 Version table: *** 1.14.2+ds1-1 500 500 http://archive.ubuntu.com/ubuntu bionic-proposed/universe amd64 Packages 100 /var/lib/dpkg/status 1.11.1+ds2-3 500 500 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages libblosc1: Installed: 1.14.2+ds1-1 Candidate: 1.14.2+ds1-1 Version table: *** 1.14.2+ds1-1 500 500 http://archive.ubuntu.com/ubuntu bionic-proposed/universe amd64 Packages 100 /var/lib/dpkg/status 1.11.1+ds2-3 500 500 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages root@f0b7772b23f5:/usr/share/doc/libblosc-dev/examples# for f in many_compressors.c multithread.c noinit.c simple.c; do gcc -o $f.out $f -lblosc && ./$f.out; done Blosc version info: 1.14.2 ($Date:: 2018-03-16 #$) Using 4 threads (previously using 1) Using blosclz compressor Compression: 400 -> 41384 (96.7x) Succesful roundtrip! Using lz4 compressor Compression: 400 -> 51510 (77.7x) Succesful roundtrip! Using lz4hc compressor Compression: 400 -> 38314 (104.4x) Succesful roundtrip! Using snappy compressor Compression: 400 -> 208526 (19.2x) Succesful roundtrip! Using zlib compressor Compression: 400 -> 22103 (181.0x) Succesful roundtrip! Using zstd compressor Compression: 400 -> 10908 (366.7x) Succesful roundtrip! Blosc version info: 1.14.2 ($Date:: 2018-03-16 #$) Using 1 threads (previously using 1) Compression: 400 -> 41384 (96.7x) Succesful roundtrip! Using 2 threads (previously using 1) Compression: 400 -> 41384 (96.7x) Succesful roundtrip! Using 3 threads (previously using 2) Compression: 400 -> 41384 (96.7x) Succesful roundtrip! Using 4 threads (previously using 3) Compression: 400 -> 41384 (96.7x) Succesful roundtrip! Blosc version info: 1.14.2 ($Date:: 2018-03-16 #$) Compression: 400 -> 41384 (96.7x) Decompression succesful! Succesful roundtrip! Blosc version info: 1.14.2 ($Date:: 2018-03-16 #$) Compression: 400 -> 41384 (96.7x) Decompression succesful! Succesful roundtrip! And also with regard to the original format incompatibility bug that prompted this report: root@f0b7772b23f5:/usr/share/doc/libblosc-dev/examples# gcc -o test test.c -lblosc root@f0b7772b23f5:/usr/share/doc/libblosc-dev/examples# ./test compress lz4 test.blosc Blosc version info: 1.14.2 ($Date:: 2018-03-16 #$) Compression: 400 -> 51420 (77.8x) Wrote test.blosc root@f0b7772b23f5:/usr/share/doc/libblosc-dev/examples# exit exit [estan@newton insight (improve-loading $%>)]$ cd [estan@newton ~]$ docker cp f0b7772b23f5:/usr/share/doc/libblosc-dev/examples/test.c . [estan@newton ~]$ docker cp f0b7772b23f5:/usr/share/doc/libblosc-dev/examples/test.blosc . [estan@newton ~]$ gcc -o test test.c -lblosc [estan@newton ~]$ ./test decompress lz4 test.blosc Blosc version info: 1.7.0 ($Date:: 2015-07-05 #$) Read test.blosc Decompression succesful! [estan@newton ~]$ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755380 Title: [FFe] Please sync c-blosc 1.14.0+ds1-1 from debian unstable to bionic (1.11.1 has format incompat bug!) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/c-blosc/+bug/1755380/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1755380] Re: [FFe] Please sync c-blosc 1.14.0+ds1-1 from debian unstable to bionic (1.11.1 has format incompat bug!)
Sorry, of course meant to run `apt-cache policy`, not `apt-cache show`. Here it is: root@f0b7772b23f5:/# apt-cache policy libblosc-dev libblosc-dev: Installed: (none) Candidate: 1.14.0+ds1-1 Version table: 1.14.0+ds1-1 500 500 http://archive.ubuntu.com/ubuntu bionic-proposed/universe amd64 Packages 1.11.1+ds2-3 500 500 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages root@f0b7772b23f5:/# -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755380 Title: [FFe] Please sync c-blosc 1.14.0+ds1-1 from debian unstable to bionic (1.11.1 has format incompat bug!) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/c-blosc/+bug/1755380/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1755380] Re: [FFe] Please sync c-blosc 1.14.0+ds1-1 from debian unstable to bionic (1.11.1 has format incompat bug!)
@adconrad Many thanks for being so quick with this. I've tested the package in -proposed: root@194d7a53ffb1:/usr/share/doc/libblosc-dev/examples# cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu Bionic Beaver (development branch)" root@194d7a53ffb1:/usr/share/doc/libblosc-dev/examples# apt-cache show libblosc-dev Package: libblosc-dev Architecture: amd64 Version: 1.14.0+ds1-1 Priority: optional Section: universe/libdevel Source: c-blosc Origin: Ubuntu Maintainer: Ubuntu DevelopersOriginal-Maintainer: Daniel Stender Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 156 Depends: libblosc1 (= 1.14.0+ds1-1) Filename: pool/universe/c/c-blosc/libblosc-dev_1.14.0+ds1-1_amd64.deb Size: 36672 MD5sum: 9a144274a54ce28f53ba0ea3fca70d13 SHA1: 4fa0a4d01b28bf33d2dbcf070e3e423bac9e6a5f SHA256: 759f694504c2a72d7ca5461ef9f4e4a9db635aabf3c941b981aa9aa266d852d3 Homepage: http://blosc.org/ Description: high performance meta-compressor optimized for binary data (development files) Description-md5: d4cb8f384fede65d372e621a91fbb94e Package: libblosc-dev Architecture: amd64 Version: 1.11.1+ds2-3 Priority: optional Section: universe/libdevel Source: c-blosc Origin: Ubuntu Maintainer: Ubuntu Developers Original-Maintainer: Daniel Stender Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 148 Depends: libblosc1 (= 1.11.1+ds2-3) Filename: pool/universe/c/c-blosc/libblosc-dev_1.11.1+ds2-3_amd64.deb Size: 35068 MD5sum: 6f2de0ec8e1542041939e65e636403ad SHA1: 8ef571cfcbf195d29f4ac9f7be7b372c21c00f22 SHA256: 1e1d1193fdfc7e9ca5b7a1d47907d2c36ac528ba8c6dbbd4ef99b5c1135c0a5c Homepage: http://blosc.org/ Description: high performance meta-compressor optimized for binary data (development files) Description-md5: d4cb8f384fede65d372e621a91fbb94e root@194d7a53ffb1:/usr/share/doc/libblosc-dev/examples# for f in many_compressors.c multithread.c noinit.c simple.c; do gcc $f.out $f -lblosc && ./$f.out; done Blosc version info: 1.14.0 ($Date:: 2018-02-23 #$) Using 4 threads (previously using 1) Using blosclz compressor Compression: 400 -> 41384 (96.7x) Succesful roundtrip! Using lz4 compressor Compression: 400 -> 51510 (77.7x) Succesful roundtrip! Using lz4hc compressor Compression: 400 -> 38314 (104.4x) Succesful roundtrip! Using snappy compressor Compression: 400 -> 208526 (19.2x) Succesful roundtrip! Using zlib compressor Compression: 400 -> 22103 (181.0x) Succesful roundtrip! Using zstd compressor Compression: 400 -> 10908 (366.7x) Succesful roundtrip! Blosc version info: 1.14.0 ($Date:: 2018-02-23 #$) Using 1 threads (previously using 1) Compression: 400 -> 41384 (96.7x) Succesful roundtrip! Using 2 threads (previously using 1) Compression: 400 -> 41384 (96.7x) Succesful roundtrip! Using 3 threads (previously using 2) Compression: 400 -> 41384 (96.7x) Succesful roundtrip! Using 4 threads (previously using 3) Compression: 400 -> 41384 (96.7x) Succesful roundtrip! Blosc version info: 1.14.0 ($Date:: 2018-02-23 #$) Compression: 400 -> 41384 (96.7x) Decompression succesful! Succesful roundtrip! Blosc version info: 1.14.0 ($Date:: 2018-02-23 #$) Compression: 400 -> 41384 (96.7x) Decompression succesful! Succesful roundtrip! root@194d7a53ffb1:/usr/share/doc/libblosc-dev/examples# I also verified that the test case from the upstream bug report that prompted the 1.14 release works as expected: root@194d7a53ffb1:~# gcc -o test test.c -lblosc root@194d7a53ffb1:~# ./test compress lz4 test.blosc Blosc version info: 1.14.0 ($Date:: 2018-02-23 #$) Compression: 400 -> 51420 (77.8x) Wrote test.blosc root@194d7a53ffb1:~# exit exit [estan@newton ~]$ docker cp 194d7a53ffb1:/root/test.blosc . [estan@newton ~]$ docker cp 194d7a53ffb1:/root/test.c . [estan@newton ~]$ gcc -o test test.c -lblosc [estan@newton ~]$ ./test decompress lz4 test.blosc Blosc version info: 1.7.0 ($Date:: 2015-07-05 #$) Read test.blosc Decompression succesful! [estan@newton ~]$ LGTM! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755380 Title: [FFe] Please sync c-blosc 1.14.0+ds1-1 from debian unstable to bionic (1.11.1 has format incompat bug!) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/c-blosc/+bug/1755380/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1755380] [NEW] Please sync c-blosc 1.14.0+ds1-1 from debian unstable to bionic (1.11.1 has format incompat bug!)
Public bug reported: We discovered a bug [1] that is present in all version of Blosc from 1.11.0 to 1.13.5 (inclusive). The bug prevents data compressed with these versions using the LZ4, LZ4HC, Zlib and Zstd compressors from being decompressed using any prior versions of Blosc (it's an accidental forward-compatiblity break). So in a sense, these versions should be considered bad apples. The bug was subsequently fixed [2] and the fix is present in the now released 1.14.0. The upstream author also blogged [3] about this incident. I alerted the Debian package maintainer (Daniel Stender) about this [4], and he was kind enough to quickly package the bugfixed version [5]. I therefore ask you to please sync this bugfixed version to bionic, since it would be unfortunate if it was released with one of the "bad" versions. Many thanks in advance! [1] https://github.com/Blosc/c-blosc/issues/215 [2] https://github.com/Blosc/c-blosc/pull/216 [3] http://blosc.org/posts/new-forward-compat-policy/ [4] https://salsa.debian.org/debian/c-blosc/merge_requests/1 [5] https://packages.debian.org/source/sid/c-blosc ** Affects: c-blosc (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755380 Title: Please sync c-blosc 1.14.0+ds1-1 from debian unstable to bionic (1.11.1 has format incompat bug!) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/c-blosc/+bug/1755380/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 364091] Re: xrandr error with delmode
Same problem No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 17.04 Release:17.04 Codename: zesty xrandr --delmode 'DVI-1' '"1368x768_60.00"' X Error of failed request: BadAccess (attempt to access private resource denied) Major opcode of failed request: 140 (RANDR) Minor opcode of failed request: 19 (RRDeleteOutputMode) Serial number of failed request: 43 Current serial number in output stream: 44 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/364091 Title: xrandr error with delmode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/x11-xserver-utils/+bug/364091/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1638695] Re: Python 2.7.12 performance regression
We'll need the package maintainers to chime in on this. Attached is a patch that disables harmful settings. ** Patch added: "0001-Disable-fpectl-and-fPIC-on-Modules-_math.c.patch" https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1638695/+attachment/4934301/+files/0001-Disable-fpectl-and-fPIC-on-Modules-_math.c.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1638695 Title: Python 2.7.12 performance regression To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1638695/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1638695] Re: Python 2.7.12 performance regression
After much testing I found what is causing the regression in 16.04 and later. There are several distinct causes which are attributed to the choices made in debian/rules and the changes in GCC. Cause #1: the decision to compile `Modules/_math.c` with `-fPIC` *and* link it statically into the python executable [1]. This causes the majority of the slowdown. This may be a bug in GCC or simply a constraint, I didn't find anything specific on this topic, although there are a lot of old bug reports regarding the interaction of -fPIC with -flto. Cause #2: the enablement of `fpectl` [2], specifically the passage of `--with-fpectl` to `configure`. fpectl is disabled in python.org builds by default and its use is discouraged. Yet, Debian builds enable it unconditionally, and it seems to cause a significant performance degradation. It's much less noticeable on 14.04 with GCC 4.8.0, but on more recent releases the performance difference seems to be larger. Plausible Cause #3: stronger stack smashing protection in 16.04, which uses --fstack-protector-strong, wherease 14.04 and earlier used --fstack-protector (with lesser performance overhead). Also, debian/rules limits the scope of PGO's PROFILE_TASK to 377 test suites vs upstream's 397, which affects performance somewhat negatively, but this is not definitive. What are the reasons behind the trimming of the tests used for PGO? Without fpectl, and without -fPIC on _math.c, 2.7.12 built on 16.04 is slower than stock 2.7.6 on 14.04 by about 0.9% in my pyperformance runs [3]. This is in contrast to a whopping 7.95% slowdown when comparing stock versions. Finally, a vanilla Python 2.7.12 build using GCC 5.4.0, default CFLAGS, default PROFILE_TASK and default Modules/Setup.local consistently runs faster in benchmarks than 2.7.6 (by about 0.7%), but I was not able to pinpoint the exact reason for that. Note: the percentages above are the relative change in the geometric mean of pyperformance benchmark results. [1] https://git.launchpad.net/~usd-import-team/ubuntu/+source/python2.7/tree/debian/rules?h=ubuntu/xenial-updates#n421 [2] https://git.launchpad.net/~usd-import- team/ubuntu/+source/python2.7/tree/debian/rules?h=ubuntu/xenial- updates#n117 [3] https://docs.google.com/spreadsheets/d/1L3_gxe- AOYJsXFwGZgFko8jaChB0dFPjK5oMO5T5vj4/edit?usp=sharing -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1638695 Title: Python 2.7.12 performance regression To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1638695/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1565048] Re: imgur upload plugin no longer works due to now unsupported API 1 and 2
Why did this PR is not merged? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1565048 Title: imgur upload plugin no longer works due to now unsupported API 1 and 2 To manage notifications about this bug go to: https://bugs.launchpad.net/shutter/+bug/1565048/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1574617] Re: External monitor keeps going blank
I too have this problem and it seems to me like it could be because of cable bad quality. I had some cheap HDMI cable and I also get blank screen now and then and it comes right back in 2 seconds. But when I changed the cable it never happened again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1574617 Title: External monitor keeps going blank To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1574617/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1598173] Re: Please consider SRU of "xcb: Compress mouse motion and touch update events"
Thank you! Been waiting for this fix for 11 months, and boy does it taste sweet now that it's here :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1598173 Title: Please consider SRU of "xcb: Compress mouse motion and touch update events" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1598173/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1380702] Re: No keyboards shortcuts in QT apps
Ah, thanks. Did not know about that page. Thanks for looking into it. (My primary interest is not actually this fix, but the mouse event compression SRU that got piggybacked into it: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource- src/+bug/1598173). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1380702 Title: No keyboards shortcuts in QT apps To manage notifications about this bug go to: https://bugs.launchpad.net/appmenu-qt5/+bug/1380702/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1380702] Re: No keyboards shortcuts in QT apps
Any idea when this will hit -updates, now that the verification is done? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1380702 Title: No keyboards shortcuts in QT apps To manage notifications about this bug go to: https://bugs.launchpad.net/appmenu-qt5/+bug/1380702/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1598173] Re: Please consider SRU of "xcb: Compress mouse motion and touch update events"
Aha, I forgot to check the other bug. No worries. Thanks a lot for all the work Dmitry, looking at that bug I see that it is much more complicated than this one. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1598173 Title: Please consider SRU of "xcb: Compress mouse motion and touch update events" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1598173/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1598173] Re: Please consider SRU of "xcb: Compress mouse motion and touch update events"
Do I need to do something more for this to be uploaded to xenial- updates? Should I try to get someone else to test? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1598173 Title: Please consider SRU of "xcb: Compress mouse motion and touch update events" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1598173/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1598173] Re: Please consider SRU of "xcb: Compress mouse motion and touch update events"
@apw: I've tested the 5.5.1+dfsg-16ubuntu7.4 in xenial-proposed with the test case I attached in comment #4, as well as the Wrapping/Python/vtk/qt/QVTKRenderWindowInteractor.py script in the VTK source, and the problem is fixed. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1598173 Title: Please consider SRU of "xcb: Compress mouse motion and touch update events" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1598173/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1598173] Re: Please consider SRU of "xcb: Compress mouse motion and touch update events"
Alright, yes lets hope. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1598173 Title: Please consider SRU of "xcb: Compress mouse motion and touch update events" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1598173/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1598173] Re: Please consider SRU of "xcb: Compress mouse motion and touch update events"
I made a couple of pings in #ubuntu-release without reply, but I guess people are just busy :) Another question though: I can see that there was already another qtbase-opensource-src upload in the queue (5.5.1+dfsg-16ubuntu7.3). Will an approver have to approve that first, or will that one be discarded and 5.5.1+dfsg-16ubuntu7.4 taken directly? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1598173 Title: Please consider SRU of "xcb: Compress mouse motion and touch update events" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1598173/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1598173] Re: Please consider SRU of "xcb: Compress mouse motion and touch update events"
I'm a little unsure what the process is now, should I tag this bug with something? Or just wait until someone comes around to approve the upload? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1598173 Title: Please consider SRU of "xcb: Compress mouse motion and touch update events" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1598173/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1598173] Re: Please consider SRU of "xcb: Compress mouse motion and touch update events"
Excellent. Many thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1598173 Title: Please consider SRU of "xcb: Compress mouse motion and touch update events" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1598173/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1598173] Re: Please consider SRU of "xcb: Compress mouse motion and touch update events"
** Description changed: Mouse event compression stopped working in Qt 5, a regression from Qt 4: -https://bugreports.qt.io/browse/QTBUG-40889 + https://bugreports.qt.io/browse/QTBUG-40889 The bug was fixed in Qt 5.6 https://codereview.qt- - project.org/#/c/126136/ where it has been thoroughly tested by now. + project.org/#/c/126136/ where the fix has been thoroughly tested by now. Attached is a debdiff against 5.5.1+dfsg-16ubuntu7.2 which includes a backport of the 5.6 patch (only one trivial hunk failed, which was easily fixed). [Impact] The bug affects any program that relies on the event compression Qt normally does. For example, VTK programs (ParaView, Tomviz, ...) do their rendering in response to mouse events during camera movements, and with event compression at the Qt level suddenly gone, camera movements become very slow, since the application is now flooded with mouse events and the rendering lags behind. The problem is not limited to these programs however; it can be observed by simply putting two regular, slightly slow-to-render, widgets into a QSplitter and moving the splitter handle. The result is a syrup-like experience as the widgets try to keep up with the onslaught of resize events due to the lack of mouse event compression. [Test Case] The attached test application can be used to check if event compression is functioning. It performs some artificial work on each mouse move and prints a message. Click and drag the mouse a little. After releasing the mouse, you'll notice that the printouts keeps coming for quite a while, as the program is catching up with the flood of events. With the attached patch (and with Qt 4), the problem is gone - the mouse event stream is compressed and the printouts are no longer lagging behind. [Regression Potential] There's a small risk that some applications have made workarounds for the faulty behavior, and that unwanted behavior is introduced if this bug is fixed. But chances are high that such workarounds will keep working, as the obvious workaround is to do timer based rendering instead of event based. The workarounds will then simply become unnecessary, but shouldn't cause problems. I'm asking for someone to nominate this bug for an SRU of 16.04 LTS. ** Description changed: Mouse event compression stopped working in Qt 5, a regression from Qt 4: https://bugreports.qt.io/browse/QTBUG-40889 The bug was fixed in Qt 5.6 https://codereview.qt- project.org/#/c/126136/ where the fix has been thoroughly tested by now. Attached is a debdiff against 5.5.1+dfsg-16ubuntu7.2 which includes a backport of the 5.6 patch (only one trivial hunk failed, which was easily fixed). [Impact] The bug affects any program that relies on the event compression Qt - normally does. For example, VTK programs (ParaView, Tomviz, ...) do + normally performs. For example, VTK programs (ParaView, Tomviz, ...) do their rendering in response to mouse events during camera movements, and with event compression at the Qt level suddenly gone, camera movements become very slow, since the application is now flooded with mouse events and the rendering lags behind. The problem is not limited to these programs however; it can be observed by simply putting two regular, slightly slow-to-render, widgets into a QSplitter and moving the splitter handle. The result is a syrup-like experience as the widgets try to keep up with the onslaught of resize events due to the lack of mouse event compression. [Test Case] The attached test application can be used to check if event compression is functioning. It performs some artificial work on each mouse move and prints a message. Click and drag the mouse a little. After releasing the mouse, you'll notice that the printouts keeps coming for quite a while, as the program is catching up with the flood of events. With the attached patch (and with Qt 4), the problem is gone - the mouse event stream is compressed and the printouts are no longer lagging behind. [Regression Potential] There's a small risk that some applications have made workarounds for the faulty behavior, and that unwanted behavior is introduced if this bug is fixed. But chances are high that such workarounds will keep working, as the obvious workaround is to do timer based rendering instead of event based. The workarounds will then simply become unnecessary, but shouldn't cause problems. I'm asking for someone to nominate this bug for an SRU of 16.04 LTS. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1598173 Title: Please consider SRU of "xcb: Compress mouse motion and touch update events" To manage notifications about this bug go to:
[Bug 1598173] Re: Please consider SRU of "xcb: Compress mouse motion and touch update events"
Dmitry: I've updated the description with the SRU template. I also attached a test case and a debdiff. I've tested that the updated package fixes the problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1598173 Title: Please consider SRU of "xcb: Compress mouse motion and touch update events" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1598173/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs