[Bug 2078704] Re: [REGRESSION] Unable to suspend-to-ram with NFS mounted on 5.15.0-119-generic
Hello, 5.15.0-121-generic is OK, there is no such problem with suspend-to-ram or suspend-to-disk. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078704 Title: [REGRESSION] Unable to suspend-to-ram with NFS mounted on 5.15.0-119-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2078704/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078704] Re: [REGRESSION] Unable to suspend-to-ram with NFS mounted on 5.15.0-119-generic
Hello, Thank you for the quick response. I'm compiling Ubuntu-hwe-5.15-5.15.0-122.132_20.04.1 (from the focal repo), will confirm it fixes the issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078704 Title: [REGRESSION] Unable to suspend-to-ram with NFS mounted on 5.15.0-119-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2078704/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078704] Re: [REGRESSION] Unable to suspend-to-ram with NFS mounted on 5.15.0-119-generic
Ah, OK, the kernel is available on https://launchpad.net/~canonical- kernel-team/+archive/ubuntu/proposed . Will check it there. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078704 Title: [REGRESSION] Unable to suspend-to-ram with NFS mounted on 5.15.0-119-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2078704/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078704] [NEW] [REGRESSION] Unable to suspend-to-ram with NFS mounted on 5.15.0-119-generic
Public bug reported:
Hello,
Since Linux 5.15.0-119-generic, I am unable to suspend-to-ram my laptop
when the NFS share from our OpenWRT router is mounted. I get the
following errors in dmesg:
[ 5205.898693] PM: suspend entry (deep)
[ 5205.918450] Filesystems sync: 0.019 seconds
[ 5205.918680] Freezing user space processes ... (elapsed 0.002 seconds) done.
[ 5205.921666] OOM killer disabled.
[ 5205.921668] Freezing remaining freezable tasks ...
[ 5225.933279] Freezing of tasks failed after 20.012 seconds (1 tasks refusing
to freeze, wq_busy=0):
[ 5225.933839] task:NFSv4 callback state:I stack:0 pid:222125 ppid: 2
flags:0x4000
[ 5225.933867] Call Trace:
[ 5225.933876]
[ 5225.933891] __schedule+0x2cd/0x890
[ 5225.933930] schedule+0x69/0x110
[ 5225.933961] nfs41_callback_svc+0x179/0x180 [nfsv4]
[ 5225.934140] ? wait_woken+0x60/0x60
[ 5225.934160] ? nfs_map_gid_to_group+0x120/0x120 [nfsv4]
[ 5225.934318] kthread+0x127/0x150
[ 5225.934338] ? set_kthread_struct+0x50/0x50
[ 5225.934359] ret_from_fork+0x1f/0x30
[ 5225.934394]
[ 5225.934412] Restarting kernel threads ... done.
[ 5225.935170] OOM killer enabled.
[ 5225.935178] Restarting tasks ... done.
[ 5225.950919] PM: suspend exit
After I unmount the share, the suspend works.
To me it seems that it is caused by the backport of the patch "nfsd:
don't allow nfsd threads to be signalled." (which got into 5.15.0-118)
and the lack of the following commit (which is present in upstream
5.15):
commit 3feac2b5529335dff4f91d3e97b006a7096d63ec
Author: NeilBrown
Date: Fri Jun 7 09:10:48 2024 -0400
sunrpc: exclude from freezer when waiting for requests:
Prior to v6.1, the freezer will only wake a kernel thread from an
uninterruptible sleep. Since we changed svc_get_next_xprt() to use
and
IDLE sleep the freezer cannot wake it. We need to tell the freezer
to
ignore it instead.
To make this work with only upstream commits, 5.15.y would need
commit f5d39b020809 ("freezer,sched: Rewrite core freezer logic")
which allows non-interruptible sleeps to be woken by the freezer.
Fixes: 9b8a8e5e8129 ("nfsd: don't allow nfsd threads to be
signalled.")
Tested-by: Jon Hunter
Signed-off-by: NeilBrown
Signed-off-by: Greg Kroah-Hartman
This was discussed earlier on LKML in this thread:
https://lore.kernel.org/all/171693973585.27191.10038342787850677...@noble.neil.brown.name/
My hardware: HP 17-by0001nw laptop
The NFS share is mounted over WiFi.
/etc/exports on the router:
/mnt/pendrive/nfs
-fsid=0,rw,sync,no_subtree_check,all_squash,anonuid=1000,anongid=1000
192.168.1.20 192.168.1.22 192.168.1.24
mount parameters on my laptop (from /etc/fstab):
192.168.1.3:/ /media/netdrive
nfs
users,noauto,exec,sync,noac,lookupcache=none,nfsvers=4.2,soft,timeo=10,retrans=2
0 0
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.15.0-119-generic 5.15.0-119.129~20.04.1
ProcVersionSignature: Ubuntu 5.15.0-119.129~20.04.1-generic 5.15.160
Uname: Linux 5.15.0-119-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: GNOME-Classic:GNOME
Date: Mon Sep 2 10:33:11 2024
InstallationDate: Installed on 2020-09-12 (1450 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=pl_PL.UTF-8
SHELL=/bin/bash
SourcePackage: linux-signed-hwe-5.15
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: linux-signed-hwe-5.15 (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug focal regression-update
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2078704
Title:
[REGRESSION] Unable to suspend-to-ram with NFS mounted on
5.15.0-119-generic
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/2078704/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059092] Re: [VROC] mdadm detects dm-device as partition
Hi I retested this with kernel 6.8.0-38-generic and I can not reproduce the issue :-) Thanks, Mateusz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059092 Title: [VROC] mdadm detects dm-device as partition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2059092/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069821] Re: [VROC] [Ub 24.04] mdadm: buffer overflow detected
Any updates on this? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069821 Title: [VROC] [Ub 24.04] mdadm: buffer overflow detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/2069821/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
I had no problem running Balena Etcher on Ubuntu 24.04 LTS. Do you have the latest version of Etcher? 1.19.16 https://github.com/balena-io/etcher/blob/master/CHANGELOG.md -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2046844 Title: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/2046844/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2036597] Re: Strange permissions and/or links to default directories in home folder (Music, Pictures, Public, Templates and Videos))
It turns out the bug isn't resolved. I don't why I thought that Gnome extension will resolve the problem in KDE snap. This is obviously a KDE program so the fix must be applied to the KDE extension. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2036597 Title: Strange permissions and/or links to default directories in home folder (Music, Pictures, Public, Templates and Videos)) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/okular/+bug/2036597/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2036597] Re: Strange permissions and/or links to default directories in home folder (Music, Pictures, Public, Templates and Videos))
Good news this bug has been resolved. https://github.com/ubuntu/gnome-sdk/issues/188 The fix is currently in the candidate channel of gnome-42-2204 content snap. I can confirm from my own testing it indeed fixes 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/2036597 Title: Strange permissions and/or links to default directories in home folder (Music, Pictures, Public, Templates and Videos)) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/okular/+bug/2036597/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2057792] Re: Some Games are crashing linked to a vm_max_map_count too low
Just updated the package from noble-proposed and the file is there with the agreed value. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2057792 Title: Some Games are crashing linked to a vm_max_map_count too low To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gamemode/+bug/2057792/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059092] [NEW] [VROC] mdadm detects dm-device as partition
Public bug reported:
We discovered an issue when trying to create imsm container with mdadm
on dm-device.
Environment:
OS: Ubuntu 24.04
Kernel: inbox 6.6.0
Scenario:
1. Create dm device
# echo -e '0 195312 linear /dev/nvme2n1 0' | dmsetup create nvme2n1DM
2. Create IMSM container.
# dmdev=$(readlink -f /dev/mapper/nvme2n1DM)
# export IMSM_DEVNAME_AS_SERIAL=1 IMSM_NO_PLATFORM=1; mdadm --create
/dev/md/container --metadata=imsm --raid-disks=1 $dmdev --force
Expected result:
Container is created.
Actual result:
Error message is displayed
# mdadm: imsm: /dev/dm-0 is a partition, cannot be used in IMSM
Container is not created.
Additional info:
Mdadm uses ioctl call underneath to check if device is a partition.
Here's the function:
int test_partition(int fd)
{
/* Check if fd is a whole-disk or a partition.
* BLKPG will return EINVAL on a partition, and BLKPG_DEL_PARTITION
* will return ENXIO on an invalid partition number.
*/
struct blkpg_ioctl_arg a;
struct blkpg_partition p;
a.op = BLKPG_DEL_PARTITION;
a.data = (void*)&p;
a.datalen = sizeof(p);
a.flags = 0;
memset(a.data, 0, a.datalen);
p.pno = 1<<30;
if (ioctl(fd, BLKPG, &a) == 0)
/* Very unlikely, but not a partition */
return 0;
if (errno == ENXIO || errno == ENOTTY)
/* not a partition */
return 0;
return 1;
}
We established that the behavior is caused by regression in ioctl.
Thread:
https://lore.kernel.org/all/caoyef9vsmqkmcqjo1k6ykgnujwn-nzfxy17n3f-cmike1ty...@mail.gmail.com/
Fix:
https://lore.kernel.org/all/20240118130401.792757-1-lilingf...@huaweicloud.com/
We established that ioctl call on dm-device returns EINVAL as if it was a
partition.
Note that this function was was working unchanged for last 10+years and the
issue was fixed in newer kenel.
** Affects: ubuntu
Importance: Undecided
Status: New
** Tags: vroc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059092
Title:
[VROC] mdadm detects dm-device as partition
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/2059092/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2036597] Re: Strange permissions and/or links to default directories in home folder (Music, Pictures, Public, Templates and Videos))
This bug isn't a bug related to just one snap. It affects all snaps that set HOME to $SNAP_REAL_HOME. It is a bug of snapd or the gnome-sdk as reported by Popey. https://github.com/ubuntu/gnome-sdk/issues/188 https://github.com/popey/dosbox-staging-snap/issues/12 https://forum.snapcraft.io/t/setting-home-in-snap-to-user-home-seems-to- cause-all-empty-user-dirs-to-become-broken-symlinks/39463 ** Bug watch added: github.com/ubuntu/gnome-sdk/issues #188 https://github.com/ubuntu/gnome-sdk/issues/188 ** Bug watch added: github.com/popey/dosbox-staging-snap/issues #12 https://github.com/popey/dosbox-staging-snap/issues/12 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2036597 Title: Strange permissions and/or links to default directories in home folder (Music, Pictures, Public, Templates and Videos)) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/okular/+bug/2036597/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1980271] Re: Snap doesn't refresh automatically immediately after snap is quit when update is pending
I'm using the edge versions of snapd and snapd-desktop-integration and the changes work. When I click the OK button with Firefox or Snap Store update and then close the app, snapd performs update. I don't have to resort to any manual tinkering (no snap refresh or killing the process from terminal). This is great improvement but I hope that eventually users will see the option to click on a button that closes the app, then applies the update and finally restarts the app. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to a duplicate bug report (1998177). https://bugs.launchpad.net/bugs/1980271 Title: Snap doesn't refresh automatically immediately after snap is quit when update is pending To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1980271/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1974029] [NEW] vram memory leak under Wayland
Public bug reported: I use 3 monitors. When I turn two of then off and on, the "memory usage" shown by nvidia-smi grows by approximately 400 MB each cycle. When used video memory reaches maximum my card has (it ix GTX 970 with 4GB) the graphical system sort of crashes (desktop is not shown, one of the monitor does not show image at all). This occurs only under Wayland. Description:Ubuntu 22.04 LTS Release:22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..0c.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 510.60.02 Wed Mar 16 11:24:05 UTC 2022 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-19ubuntu1) ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed May 18 14:50:11 2022 DistUpgraded: 2022-03-19 09:03:59,252 INFO cache.commit() DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/510.60.02, 5.15.0-27-generic, x86_64: installed nvidia/510.60.02, 5.15.0-30-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GM204 [GeForce GTX 970] [10de:13c2] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd GM204 [GeForce GTX 970] [1458:367a] MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-30-generic root=UUID=ca73c670-cd82-4bb7-9d49-1e036cf94a1a ro usbcore.autosuspend=-1 libata.force=1.00:noncq acpi_enforce_resources=lax libata.noacpi=1 amd_iommu=on iommu=pt SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-03-19 (60 days ago) dmi.bios.date: 08/10/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5861 dmi.board.asset.tag: Default string dmi.board.name: PRIME X470-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5861:bd08/10/2021:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX470-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer mtime.conffile..etc.apport.crashdb.conf: 2021-05-03T18:07:38.595923 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubuntu wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1974029 Title: vram memory leak under Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1974029/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972255] Re: do-release-upgrade fails to upgrade 20.04 -> 22.04 when run from chroot
*** This bug is a duplicate of bug 1965568 *** https://bugs.launchpad.net/bugs/1965568 > You could check /var/log/dist-upgrade/main.log and see if you have the same error message I do not have /var/log/dist-upgrade/main.log for failing run now. :( Trying next time, I will save /var/log/dist-upgrade/main.log in case of error and open new bug report. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972255 Title: do-release-upgrade fails to upgrade 20.04 -> 22.04 when run from chroot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1972255/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972255] [NEW] do-release-upgrade fails to upgrade 20.04 -> 22.04 when run from chroot
Public bug reported: When running do-release-upgrade in 20.04 chroot it fails without any error/reason returning back to shell: # do-release-upgrade -d Checking for a new Ubuntu release Get:1 Upgrade tool signature [819 B] Get:2 Upgrade tool [1261 kB] Fetched 1262 kB in 0s (0 B/s) authenticate 'jammy.tar.gz' against 'jammy.tar.gz.gpg' extracting 'jammy.tar.gz' [screen is terminating] # lsb_release -rd Description:Ubuntu 20.04.4 LTS Release:20.04 ** Affects: 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/1972255 Title: do-release-upgrade fails to upgrade 20.04 -> 22.04 when run from chroot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1972255/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964333] Re: window decoration glitch with nvidia driver 495 and 510
Thank you. Frankly I cannot continue to provide information on that bug. In the meantime I have upgraded to 22.04. And this particular issue vanished for me. As far as I am concerned the issue does not exist any more. It still occurs at my computer at work, but there I have the Debian 11, and I guess this is not the right place to follow it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964333 Title: window decoration glitch with nvidia driver 495 and 510 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-495/+bug/1964333/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971577] Re: unable to distinquish different bluetooth devices
This is the screenshot of the Bluetooth settings menu. ** Attachment added: "Screenshot from 2022-05-04 14-49-39.png" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1971577/+attachment/5586674/+files/Screenshot%20from%202022-05-04%2014-49-39.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971577 Title: unable to distinquish different bluetooth devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1971577/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971577] [NEW] unable to distinquish different bluetooth devices
Public bug reported: In "bluetooth" panel of the settings there are connected/presiously connected devices. In case some one owns multiple devices of same model it is impossible to distinguish them easily. In practice different entries are distinguishable by the bluetooth device address. There should be an option to "rename" the device to a string set by the used. There is such an option in MacOS. In my use case I own several Bluetooth rechargeable headsets. They need to be charged for 4 hours to allow for 6-8 hours of use. So I own several copies to have entire-day coverage. In real world the headsets are distinguishable by the state of cushions, but quite often I have one headset connected, but I do not know which one is it. If I could rename: Philips SHB7150 Philips SHB7150 Philips SHB7150 Philips SHB7150 to e.g. Philips SHB7150 - mint cushions Philips SHB7150 - worn cushions Philips SHB7150 - extra battery Philips SHB7150 - number 4 this would be very helpful. This is not really a "bug" but a missing functionality. Description:Ubuntu 22.04 LTS Release:22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed May 4 14:49:59 2022 EcryptfsInUse: Yes SourcePackage: nautilus UpgradeStatus: Upgraded to jammy on 2022-03-19 (46 days ago) mtime.conffile..etc.apport.crashdb.conf: 2021-05-03T18:07:38.595923 usr_lib_nautilus: evince42.1-3 file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy 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/1971577 Title: unable to distinquish different bluetooth devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1971577/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962718] Re: Firefox snap crashes on every upgrade
The snapd changes got merged in March and I think this is fixed. I first switched to the candidate channel and it didn't crash Firefox. Today I switched to beta and it also didn't crash Firefox. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962718 Title: Firefox snap crashes on every upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1962718/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969628] [NEW] Used memory indication is not really useful
Public bug reported: The values shown as "memory used" are not really informative. Roughly speaking "used" memory (indicated in the tool) = "really used" memory (NOT indicated in the tool) + "cache" (indicated in the tool) + "available" (NOT indicated in the tool) The tool shows the LHS "used memory" and "cache", but does not show the "available memory". With modern kernels the tendency is to "use" memory as much as possible in various buffers, so the value indicated in that tool has no practical value. For a user I would presume that "memory" should be indication of "really used" memory, because only that tells him how many application will he be able to run. Currently my Machine tells me it is using 61 GB of memory, with 20.5 GB in Cache. While all I have open are some basic simple tools like skype, Gnome-Terminal and a few Google Chrome windows. Thing is I have 33GB in "available" (according to TOP), which tells me that I am "really using" around 7GB of memory, which sounds about right. There is no way to get the 7GB value from gnome-system-monitor. The gnome-system-monitor should show "really used memory" or at the very least show also "available" memory just below "cache". ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-system-monitor 42.0-1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Apr 20 16:07:09 2022 SourcePackage: gnome-system-monitor UpgradeStatus: Upgraded to jammy on 2022-03-19 (32 days ago) mtime.conffile..etc.apport.crashdb.conf: 2021-05-03T18:07:38.595923 ** Affects: gnome-system-monitor (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ** Attachment added: "Screenshot from 2022-04-20 16-07-21.png" https://bugs.launchpad.net/bugs/1969628/+attachment/5581831/+files/Screenshot%20from%202022-04-20%2016-07-21.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969628 Title: Used memory indication is not really useful To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1969628/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969601] [NEW] context menu cut, after screen resolution is changed
Public bug reported: I have a 4K monitor. If I open Nautilus window when display is in 1920x1080 resolution, then change the resolution to 3840x2160 AND change "scaling" to 200% then the context menu appears cut. Changing the resolution and leaving "scaling" at 100% does not trigger the bug. That is the content is scaled by 200% correctly, but the bounds of the context menu window seems not transformed and is twice too small to fit the content. When I open a new window (I do not need to kill already opened window). Then the right-click context menu is fine, in the new window. In the "old" window it remains cut. No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.04 LTS Release:22.04 Codename: jammy nautilus: Installed: 1:42.0-1ubuntu2 Candidate: 1:42.0-1ubuntu2 Version table: *** 1:42.0-1ubuntu2 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Apr 20 11:17:59 2022 SourcePackage: nautilus UpgradeStatus: Upgraded to jammy on 2022-03-19 (32 days ago) mtime.conffile..etc.apport.crashdb.conf: 2021-05-03T18:07:38.595923 usr_lib_nautilus: evince42.1-3 file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages ** Attachment added: "Screenshot from 2022-04-20 11-16-58.png" https://bugs.launchpad.net/bugs/1969601/+attachment/5581674/+files/Screenshot%20from%202022-04-20%2011-16-58.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969601 Title: context menu cut, after screen resolution is changed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1969601/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967480] [NEW] GUI error in "compress file". Menu content is wider than menu window.
Public bug reported: When I click "compress.." from Nautilus, the menu that allows to change compression format is obscured (screen attached) Description:Ubuntu Jammy Jellyfish (development branch) Release:22.04 ii gnome-sushi 41.0-3 amd64sushi is a quick previewer for nautilus ii libnautilus-extension1a:amd64 1:42.0-1ubuntu2 amd64libraries for nautilus components - runtime version ii nautilus 1:42.0-1ubuntu2 amd64file manager and graphical shell for GNOME ii nautilus-data 1:42.0-1ubuntu2 all data files for nautilus ii nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 amd64GNOME terminal emulator application - Nautilus extension ii nautilus-sendto 3.8.6-4 amd64easily send files via email from within Nautilus ii nautilus-share0.7.3-2ubuntu5 amd64Nautilus extension to share folder using Samba ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 1 10:43:11 2022 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: nautilus UpgradeStatus: Upgraded to jammy on 2022-03-19 (13 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2021-05-03T18:07:38.595923 usr_lib_nautilus: evince42.1-1 file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu5 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages ** Attachment added: "Screenshot from 2022-04-01 10-41-07.png" https://bugs.launchpad.net/bugs/1967480/+attachment/5575557/+files/Screenshot%20from%202022-04-01%2010-41-07.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967480 Title: GUI error in "compress file". Menu content is wider than menu window. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1967480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1964333] Re: window decoration glitch with nvidia driver 495 and 510
Well it doesn't work: user@computer:~$ apport-collect 1964333 Package nvidia-graphics-drivers-495 not installed and no hook available, ignoring Package nvidia-graphics-drivers-510 not installed and no hook available, ignoring *** Updating problem report No additional information collected. Press any key to continue... No pending crash reports. Try --help for more information. user@computer:~$ sudo apt install nvidia-graphics-drivers-510 [sudo] password for lacki: Reading package lists... Done Building dependency tree... Done Reading state information... Done E: Unable to locate package nvidia-graphics-drivers-510 Best, Mateusz On Tue, 2022-03-29 at 19:55 +, Paul White wrote: > Thank you for taking the time to report this bug and helping to make > Ubuntu better. > > Please execute the following command only once, as it will > automatically > gather debugging information, in a terminal: > > apport-collect 1964333 > > and than change the status of each bug task back to 'New'. > > When reporting bugs in the future please use apport by using 'ubuntu- > bug' and the name of the package affected. You can learn more about > this > functionality at https://wiki.ubuntu.com/ReportingBugs. > > ** Package changed: ubuntu => nvidia-graphics-drivers-510 (Ubuntu) > > ** Also affects: nvidia-graphics-drivers-495 (Ubuntu) > Importance: Undecided > Status: New > > ** Tags added: impish > > ** Changed in: nvidia-graphics-drivers-495 (Ubuntu) > Status: New => Incomplete > > ** Changed in: nvidia-graphics-drivers-510 (Ubuntu) > Status: New => Incomplete > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964333 Title: window decoration glitch with nvidia driver 495 and 510 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-495/+bug/1964333/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964964] Re: libayatana-appindicator 0.5.90-7 breaks libappindicator3-1
As far as I know the updated packages are in proposed. I enabled it yesterday and got them as update. No indicators were removed only the libappindicator3-1 package. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964964 Title: libayatana-appindicator 0.5.90-7 breaks libappindicator3-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libayatana-appindicator/+bug/1964964/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964333] [NEW] window decoration glitch with nvidia driver 495 and 510
Public bug reported: With Ubuntu 21.10, with nvidia driver package 495 and 510 I have the graphics glitch after each login. The icons in the top bad of the window seem distorted by their upscaled "shadows" This can be removed by restarting the gnome-shell (alt+f2 and then "r" command). Under 470 no such error exist, Description:Ubuntu 21.10 Release:21.10 PS. It seems to me attaching two files to a bug report is not possible. Can it be added? ** Affects: ubuntu Importance: Undecided Status: New ** Attachment added: "with glitch and without glitch" https://bugs.launchpad.net/bugs/1964333/+attachment/5567332/+files/Screenshot%20from%202022-03-09%2011-32-31.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964333 Title: window decoration glitch with nvidia driver 495 and 510 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1964333/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1963805] [NEW] Failed to grab modeset ownership
Public bug reported: Starting from package 495, I notice lots of messages like that in dmesg: [89502.662730] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to grab modeset ownership [89502.662850] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to grab modeset ownership [89502.662899] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to grab modeset ownership [89502.662944] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to grab modeset ownership [92090.669597] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to grab modeset ownership [92090.669715] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to grab modeset ownership [92090.669766] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to grab modeset ownership [92090.669813] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to grab modeset ownershi With 495 it was 1 message after boot, and one after each waking up of the monitor from sleep. With 510 there are numerous error messages per wake up. I have followed up with nvidia: https://forums.developer.nvidia.com/t/ubuntu-21-10-failed-to-grab-modeset-ownership-with-495-44/193867/35 but ultimately their employee tells that this is expected behavour, and something else triggers the message. [quote="amrits, post:37, topic:193867, full:true"] HI All, The warning message is expected. When a client (such as the modesetting driver) attempts to open our DRM device node while modesetting permission is already acquired by something else (like the NVIDIA X driver), it has to fail, but the kernel won’t let us return a failure after v5.9-rc1, so we print this message. It won’t impact functionality of the NVIDIA X driver that already has modesetting permission. Safe to ignore as long as long as you didn’t need the other client to actually get modesetting permission. If you want to suppress the error, you would need to find which client is attempting to open the NVIDIA DRM device node and prevent it from doing so. [/quote] I use Ubuntu 21.10 with all updates. Description:Ubuntu 21.10 Release:21.10 nvidia-headless-510: Installed: (none) Candidate: 510.54-0ubuntu0.21.10.1 Version table: 510.54-0ubuntu0.21.10.1 500 500 http://pl.archive.ubuntu.com/ubuntu impish-proposed/restricted amd64 Packages 510.47.03-0ubuntu0.21.10.1 500 500 http://pl.archive.ubuntu.com/ubuntu impish-updates/restricted amd64 Packages 500 http://security.ubuntu.com/ubuntu impish-security/restricted amd64 Packages nvidia-compute-utils-510: Installed: 510.54-0ubuntu0.21.10.1 Candidate: 510.54-0ubuntu0.21.10.1 Version table: *** 510.54-0ubuntu0.21.10.1 500 500 http://pl.archive.ubuntu.com/ubuntu impish-proposed/restricted amd64 Packages 100 /var/lib/dpkg/status 510.47.03-0ubuntu0.21.10.1 500 500 http://pl.archive.ubuntu.com/ubuntu impish-updates/restricted amd64 Packages 500 http://security.ubuntu.com/ubuntu impish-security/restricted amd64 Packages nvidia-dkms-510: Installed: 510.54-0ubuntu0.21.10.1 Candidate: 510.54-0ubuntu0.21.10.1 Version table: *** 510.54-0ubuntu0.21.10.1 500 500 http://pl.archive.ubuntu.com/ubuntu impish-proposed/restricted amd64 Packages 100 /var/lib/dpkg/status 510.47.03-0ubuntu0.21.10.1 500 500 http://pl.archive.ubuntu.com/ubuntu impish-updates/restricted amd64 Packages 500 http://security.ubuntu.com/ubuntu impish-security/restricted amd64 Packages nvidia-driver-510: Installed: 510.54-0ubuntu0.21.10.1 Candidate: 510.54-0ubuntu0.21.10.1 Version table: *** 510.54-0ubuntu0.21.10.1 500 500 http://pl.archive.ubuntu.com/ubuntu impish-proposed/restricted amd64 Packages 100 /var/lib/dpkg/status 510.47.03-0ubuntu0.21.10.1 500 500 http://pl.archive.ubuntu.com/ubuntu impish-updates/restricted amd64 Packages 500 http://security.ubuntu.com/ubuntu impish-security/restricted amd64 Packages nvidia-utils-510: Installed: 510.54-0ubuntu0.21.10.1 Candidate: 510.54-0ubuntu0.21.10.1 Version table: *** 510.54-0ubuntu0.21.10.1 500 500 http://pl.archive.ubuntu.com/ubuntu impish-proposed/restricted amd64 Packages 100 /var/lib/dpkg/status 510.47.03-0ubuntu0.21.10.1 500 500 http://pl.archive.ubuntu.com/ubuntu impish-updates/restricted amd64 Packages 500 http://security.ubuntu.com/ubuntu impish-security/restricted amd64 Packages nvidia-kernel-common-510: Installed: 510.54-0ubuntu0.21.10.1 Candidate: 510.54-0ubuntu0.21.10.1 Version table: *** 510.54-0ubuntu0.21.10.1 500 500 http://pl.archive.ubuntu.com/ubuntu impish-proposed/restricted amd64 Packages 100 /var/lib/dpkg/status 510.47
[Bug 1957154] [NEW] Can't boot after kernel 5.11.0-44 update
Public bug reported: - With kernel 5.11.0-41 everything is ok. - Choosing updated kernel 5.11.0-44 or 5.11.0-46 in Grub results in glitch lines at top of screen and instant reboot. - It may be related to nvidia-driver-470? ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-44-generic 5.11.0-44.48 ProcVersionSignature: Ubuntu 5.11.0-41.45-generic 5.11.22 Uname: Linux 5.11.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: adam 1523 F mate-settings-d adam 1928 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Wed Jan 12 10:00:59 2022 InstallationDate: Installed on 2021-10-03 (101 days ago) InstallationMedia: Ubuntu-MATE 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Dell Inc. Precision T3600 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-41-generic root=UUID=014ec6ad-d170-40b9-8b77-af7620c76daf ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-41-generic N/A linux-backports-modules-5.11.0-41-generic N/A linux-firmware 1.197.5 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/21/2018 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 08HPGT dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA17:bd06/21/2018:br4.6:svnDellInc.:pnPrecisionT3600:pvr01:sku:rvnDellInc.:rn08HPGT:rvrA01:cvnDellInc.:ct7:cvr: dmi.product.name: Precision T3600 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute 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/1957154 Title: Can't boot after kernel 5.11.0-44 update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957154/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887372] Re: Cannot create lvm upon IMSM raid array
Jeff, we verified it is no longer an issue on Focal. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887372 Title: Cannot create lvm upon IMSM raid array To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1887372/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900851] Re: [SRU] Cannot Create Port with Fixed IP Address
@hopem is there any ETA when 18.3.4 will be available for Ussuri? Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900851 Title: [SRU] Cannot Create Port with Fixed IP Address To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1900851/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1815101] Re: [master] Restarting systemd-networkd breaks keepalived, heartbeat, corosync, pacemaker (interface aliases are restarted)
I've tested 237-3ubuntu10.50+testpkg20210802b3 the ppa and it resolves the issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1815101 Title: [master] Restarting systemd-networkd breaks keepalived, heartbeat, corosync, pacemaker (interface aliases are restarted) To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1815101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925320] Re: Backport packages for 20.04.3 HWE stack
I've checked both my install and daily live image of focal. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925320 Title: Backport packages for 20.04.3 HWE stack To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/1925320/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934783] Re: Graphical glitches with Mesa 21.0.3 on AMD Radeon RX 5600 XT
** Tags removed: verification-needed-hirsute ** Tags added: verification-done-hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934783 Title: Graphical glitches with Mesa 21.0.3 on AMD Radeon RX 5600 XT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1934783/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934783] Re: Graphical glitches with Mesa 21.0.3 on AMD Radeon RX 5600 XT
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934783 Title: Graphical glitches with Mesa 21.0.3 on AMD Radeon RX 5600 XT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1934783/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934783] Re: Graphical glitches with Mesa 21.0.3 on AMD Radeon RX 5600 XT
I used the hirsute LiveCD again and it has mesa 21.0.1. I refreshed apt but there wasn't any update of mesa. So I enabled hirsute-proposed and upgraded mesa to 21.0.3. Then I logged out and straight away there were glitches on the login screen. I've logged in and confirmed that Gnome Shell and programs now also have graphical glitches. Then I used the ppa and it solved the problem. So I confirm that the fix works. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934783 Title: Graphical glitches with Mesa 21.0.3 on AMD Radeon RX 5600 XT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1934783/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934783] Re: Graphical glitches with Mesa 21.0.3 on AMD Radeon RX 5600 XT
But I didn't had problems with hirsute LiveCD. And my install is focal. I've tried the ppa with release changed to hirsute but focal can't be upgraded due to conflicts. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934783 Title: Graphical glitches with Mesa 21.0.3 on AMD Radeon RX 5600 XT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1934783/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934783] Re: Graphical glitches with Mesa 21.0.3 on AMD Radeon RX 5600 XT
I've found that other people with RX 5600 XT had problems with this version of mesa. https://bugs.archlinux.org/task/70554 https://gitlab.freedesktop.org/mesa/mesa/-/issues/4691 There is a new release of mesa (21.0.3-2) that fixes the problem for those users. Hope that you upload it to focal-proposed. ** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #4691 https://gitlab.freedesktop.org/mesa/mesa/-/issues/4691 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934783 Title: Graphical glitches with Mesa 21.0.3 on AMD Radeon RX 5600 XT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1934783/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934783] Re: Graphical glitches with Mesa 21.0.3 on AMD Radeon RX 5600 XT
Hirsute live image works without problems. That has mesa versioned as 21.0.1. So it looks like the problem is in 21.0.3 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934783 Title: Graphical glitches with Mesa 21.0.3 on AMD Radeon RX 5600 XT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1934783/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934783] Re: Graphical glitches with Mesa 21.0.3 on AMD Radeon RX 5600 XT
I've checked the latest focal live image and it has the exact same glitches as my install. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934783 Title: Graphical glitches with Mesa 21.0.3 on AMD Radeon RX 5600 XT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1934783/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925320] Re: Backport packages for 20.04.3 HWE stack
I've filed a separate bug. https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1934783 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925320 Title: Backport packages for 20.04.3 HWE stack To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/1925320/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934783] [NEW] Graphical glitches with Mesa 21.0.3 on AMD Radeon RX 5600 XT
Public bug reported: Since the update to Mesa 21.0.3 I have graphical glitches in desktop: Unity, Gnome Shell both sessions (X.org and Wayland). Also most of the programs have glitches. However Firefox seems unaffected. CPU: Info: 6-Core AMD Ryzen 5 3600 [MT MCP] speed: 3916 MHz min/max: 2200/3600 MHz Graphics: Device-1: AMD Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] driver: amdgpu v: kernel Display: x11 server: X.Org 1.20.11 driver: loaded: amdgpu,ati unloaded: fbdev,modesetting,radeon,vesa resolution: 1920x1080~60Hz OpenGL: renderer: AMD Radeon RX 5600 XT (NAVI10 DRM 3.35.0 5.4.0-79-generic LLVM 12.0.0) v: 4.6 Mesa 21.0.3 ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Tags: focal ** Attachment added: "Gnome Shell glitches.jpg" https://bugs.launchpad.net/bugs/1934783/+attachment/5509398/+files/Gnome%20Shell%20glitches.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934783 Title: Graphical glitches with Mesa 21.0.3 on AMD Radeon RX 5600 XT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1934783/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925320] Re: Backport packages for 20.04.3 HWE stack
I've got updates for mesa 21.0.1-2 July 1st and it was upgrade from 20.2.6 which worked without such problems. Then July 2nd there was upgrade to 21.0.3-0. I'm not sure if the problems started with 21.0.1. Also there are programs that work without graphical glitches. Suprisingly Firefox doesn't have problems but my main webbrowser Vivaldi does. Also I was able to watch Amazon Prime using ElectronPlayer the videos display without glitches however the menus of that program do have glitches. Also I've checked LiveCD image of Impish and there wasn't any problems with that. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925320 Title: Backport packages for 20.04.3 HWE stack To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/1925320/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925320] Re: Backport packages for 20.04.3 HWE stack
In my case the new mesa causes graphical glitches. It happens in Unity and Gnome Shell both X.org and Wayland sessions. CPU: Info: 6-Core AMD Ryzen 5 3600 [MT MCP] speed: 3916 MHz min/max: 2200/3600 MHz Graphics: Device-1: AMD Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] driver: amdgpu v: kernel Display: x11 server: X.Org 1.20.11 driver: loaded: amdgpu,ati unloaded: fbdev,modesetting,radeon,vesa resolution: 1920x1080~60Hz OpenGL: renderer: AMD Radeon RX 5600 XT (NAVI10 DRM 3.35.0 5.4.0-79-generic LLVM 12.0.0) v: 4.6 Mesa 21.0.3 I also have kernels from XanMod 5.12.13 and 5.13 and when using those there is the same problem. ** Attachment added: "Unity glitches.jpg" https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1925320/+attachment/5508947/+files/Unity%20glitches.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925320 Title: Backport packages for 20.04.3 HWE stack To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/1925320/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931684] [NEW] cdc_acm: acm_port_activate - usb_submit_urb(ctrl irq) failed
Public bug reported: Ubuntu 18.04.5 LTS Recently, after kernel update 4.15.0.144 (didn't know about the case yet), i can't open serial ports on USB CDC devices (STM32 Virtual COMs in my case). using simple cat command (with or without sudo): $ sudo cat /dev/ttyACM1 cat: /dev/ttyACM1: Input/output error or some serial programs: Failed to connect to /dev/ttyACM1 : [Errno 5] could not open port /dev/ttyACM1: [Errno 5] Input/output error: '/dev/ttyACM1' dmesg: [ 3295.718270] cdc_acm 1-2:1.0: ttyACM1: USB ACM device [ 3302.508356] cdc_acm 1-2:1.0: acm_port_activate - usb_submit_urb(ctrl irq) failed [ 3302.508940] cdc_acm 1-2:1.0: acm_port_activate - usb_submit_urb(ctrl irq) failed When i try spamming commands while plugging the device in, i am sometimes able to open the port (might be the clue). When i booted in ubuntu advanced mode to 4.15.0.143 kernel, everything started to work normally. Also tried HWE stack with 5.4.0.74 kernel, but the bug was also present there. ** Affects: ubuntu Importance: Undecided Status: New ** Tags: acm cdc port serial usb -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931684 Title: cdc_acm: acm_port_activate - usb_submit_urb(ctrl irq) failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1931684/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917451] Re: audacious audacious-plugins dependancy issue
You are using some kind packages from ppa, not official packages. At first please clear depends on your system and next install audacious from main repository. ** Changed in: audacious (Ubuntu) Status: New => Invalid ** Changed in: audacious-plugins (Ubuntu) Status: New => Invalid ** Changed in: audacious (Ubuntu) Assignee: (unassigned) => Mateusz Łukasik (mati75) ** Changed in: audacious-plugins (Ubuntu) Assignee: (unassigned) => Mateusz Łukasik (mati75) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917451 Title: audacious audacious-plugins dependancy issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/audacious/+bug/1917451/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1926956] Re: nautilus crashes when clicking on a mounted phone
Hi,thank you for your reply. Unfortunately there were no crashes in /var/crash that were related nor there was a "whoopsie". I will try to reproduce the crash, so far my initial attempts have failed. Best,Mateusz On Mon, 2021-05-03 at 13:32 +, Sebastien Bacher wrote: > Thank you for taking the time to report this bug and helping to > makeUbuntu better. It sounds like some part of the system has > crashed. Tohelp us find the cause of the crash please follow these > steps: > 1. Look in /var/crash for crash files and if found run:ubuntu-bug > YOURFILE.crashThen tell us the ID of the newly-created bug. > 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID > whereID is the content of file /var/lib/whoopsie/whoopsie-id on the > machine.Do you find any links to recent problems on that page? If so then > pleasesend the links to us. > 3. If step 2 also failed then apply the workaround from bug > 994921,reboot, reproduce the crash, and retry step 1. > Please take care to avoid attaching .crash files to bugs as we > areunable to process them as file attachments. It would also be a > securityrisk for yourself. > ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low > ** Changed in: nautilus (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926956 Title: nautilus crashes when clicking on a mounted phone To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1926956/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926956] [NEW] nautilus crashes when clicking on a mounted phone
Public bug reported: Mounted share (phone) went to sleep (lock screen activated), but the share was still mounted. I logged in to the phone at almost the same time when I clicked the mount in nautilus, which caused it to crash. May 3 14:58:41 testosteron org.gnome.Nautilus[21582]: ** May 3 14:58:41 testosteron org.gnome.Nautilus[21582]: ERROR:../src/nautilus-bookmark.c:372:nautilus_bookmark_connect_file: assertion failed: (!nautilus_file_is_gone (bookmark->file)) May 3 14:58:41 testosteron org.gnome.Nautilus[21582]: Bail out! ERROR:../src/nautilus-bookmark.c:372:nautilus_bookmark_connect_file: assertion failed: (!nautilus_file_is_gone (bookmark->file)) Best, Mateusz ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 3 15:01:51 2021 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'347' b'org.gnome.nautilus.window-state' b'initial-size' b'(1204, 765)' b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']" SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: dropbox 2020.03.04 ** Affects: nautilus (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/1926956 Title: nautilus crashes when clicking on a mounted phone To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1926956/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926144] [NEW] Flickering screen
Public bug reported: Hello, I want to report that i have some issue with my screen. I tried a lot of thinks to repair it but it does not want go. I mean, I have problem with flickering on the screen. Sometimes it's just a part of the screen flickering, at other times it is flickering of the entire screen so I cannot do normal work, and at other times there is no flickering. I reinstalled Ubuntu 3 or 4 times but still have the same problem. Of course, I did not have this problem for about two months of using Ubuntu but this problem showed up suddenly, afer one day. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Brak dostępu: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 26 12:11:20 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21fb] InstallationDate: Installed on 2021-04-19 (7 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 23567Z6 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=323971d7-dc0c-499a-bfaf-9bbb0ad9d7cd ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/16/2015 dmi.bios.release: 2.63 dmi.bios.vendor: LENOVO dmi.bios.version: G7ETA3WW (2.63 ) dmi.board.asset.tag: Not Available dmi.board.name: 23567Z6 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: N0580722 dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.15 dmi.modalias: dmi:bvnLENOVO:bvrG7ETA3WW(2.63):bd04/16/2015:br2.63:efr1.15:svnLENOVO:pn23567Z6:pvrThinkPadT430s:rvnLENOVO:rn23567Z6:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430s dmi.product.name: 23567Z6 dmi.product.sku: LENOVO_MT_2356 dmi.product.version: ThinkPad T430s dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926144 Title: Flickering screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1926144/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895246] Re: Plugin calls the incorrect API
I will fix it soon. ** Changed in: xfce4-weather-plugin (Ubuntu) Assignee: (unassigned) => Mateusz Łukasik (mati75) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895246 Title: Plugin calls the incorrect API To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-weather-plugin/+bug/1895246/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917432] [NEW] vlc does not show video, but shows two progress bars
Public bug reported: When I play an mp4 file: Wyklad2_HQ.mp4: ISO Media, MP4 Base Media v1 [IS0 14496-12:2003] (more details below) the VLC window is black (audio plays ok), but the progress bars is shown twice (both copies fully functional). One is at the bottom of the window, as it should be. The other copy is through the middle (horizontally) of the window. The menu is hidden by a black rectangle. *** system info *** (I presume will be attached automatically by the ubuntu bug tool) *** ffprobe of the video file *** ffprobe version 4.2.4-1ubuntu0.1 Copyright (c) 2007-2020 the FFmpeg developers built with gcc 9 (Ubuntu 9.3.0-10ubuntu2) configuration: --prefix=/usr --extra-version=1ubuntu0.1 --toolchain=hardened --libdir=/usr/lib/x86_64-linux-gnu --incdir=/usr/include/x86_64-linux-gnu --arch=amd64 --enable-gpl --disable-stripping --enable-avresample --disable-filter=resample --enable-avisynth --enable-gnutls --enable-ladspa --enable-libaom --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libcdio --enable-libcodec2 --enable-libflite --enable-libfontconfig --enable-libfreetype --enable-libfribidi --enable-libgme --enable-libgsm --enable-libjack --enable-libmp3lame --enable-libmysofa --enable-libopenjpeg --enable-libopenmpt --enable-libopus --enable-libpulse --enable-librsvg --enable-librubberband --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libssh --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx265 --enable-libxml2 --enable-libxvid --enable-libzmq --enable-libzvbi --enable-lv2 --enable-omx --enable-openal --enable-opencl --enable-opengl --enable-sdl2 --enable-libdc1394 --enable-libdrm --enable-libiec61883 --enable-nvenc --enable-chromaprint --enable-frei0r --enable-libx264 --enable-shared libavutil 56. 31.100 / 56. 31.100 libavcodec 58. 54.100 / 58. 54.100 libavformat58. 29.100 / 58. 29.100 libavdevice58. 8.100 / 58. 8.100 libavfilter 7. 57.100 / 7. 57.100 libavresample 4. 0. 0 / 4. 0. 0 libswscale 5. 5.100 / 5. 5.100 libswresample 3. 5.100 / 3. 5.100 libpostproc55. 5.100 / 55. 5.100 Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'Wyklad2_HQ.mp4': Metadata: major_brand : isom minor_version : 512 compatible_brands: isomiso2avc1mp41 encoder : Lavf58.29.100 Duration: 01:17:07.77, start: 0.016016, bitrate: 15244 kb/s Stream #0:0(und): Video: h264 (High) (avc1 / 0x31637661), yuv420p, 1920x1080, 15039 kb/s, 60 fps, 60 tbr, 15360 tbn, 120 tbc (default) Metadata: handler_name: VideoHandler Stream #0:1(und): Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 192 kb/s (default) Metadata: handler_name: SoundHandler ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: vlc 3.0.9.2-1 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp nvidia_modeset zcommon znvpair nvidia ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Mar 2 10:13:57 2021 SourcePackage: vlc UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: vlc (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/1917432 Title: vlc does not show video, but shows two progress bars To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vlc/+bug/1917432/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917364] [NEW] gio mount does not mount Time Capsule SMB1 share, reports errors in a misleading way
Public bug reported: gio mount does not work properly with a Samba share, reports errors in a misleading way Situation: - the share is created by Apple’s Time Capsule, that shares attached USB disks via “device password” option (setting to “accounts with passwords” option also applies to this report). The protocol version in SMB1 (disabled by default) - the client system runs on Ubuntu 20.04, with gio version 2.64.6, - the client system has /etc/samba/smb.conf which allows to connect via smbclient, however gio mount quits with “” error. The authentication-related contents of /etc/samba/smb.conf are (referred to as Config A): /etc/samba/smb.conf (fragment) - Config A ** client min protocol = NT1 client max protocol = NT1 client use spnego = no client ntlmv2 auth = no ntlm auth = yes - changing configuration of has /etc/samba/smb.conf to (Config B): /etc/samba/smb.conf (fragment) - Config A ** workgroup = WORKGROUP client min protocol = NT1 client max protocol = NT1 #client use spnego = no #client ntlmv2 auth = no #ntlm auth = yes results in gio mount asking for a password, but when a correct password is entered, the password request is repeated (endlessly). As a contrast smbclient ceases to connect with the error message: Server does not support EXTENDED_SECURITY but 'client use spnego = yes' and 'client ntlmv2 auth = yes' is set session setup failed: NT_STATUS_ACCESS_DENIED runnig gsvd -d option gives the following logs: ** Config A *** The error in the terminal invoking the gio mount command is: gio: smb:///data/: Failed to mount Windows share: No such file or directory smb: g_vfs_backend_smb_init: default workgroup = 'NULL' smb: Added new job source 0x5645821c0080 (GVfsBackendSmb) smb: Queued new job 0x5645821c1180 (GVfsJobMount) smb: do_mount - URI = smb:///data smb: do_mount - try #0 smb: auth_callback - kerberos pass smb: auth_callback - out: last_user = '', last_domain = 'WORKGROUP' smb: do_mount - [smb:///data; 0] res = -1, cancelled = 0, errno = [1] 'Operation not permitted' smb: do_mount - enabling NTLMSSP fallback smb: do_mount - try #1 smb: auth_callback - ccache pass smb: auth_callback - out: last_user = '', last_domain = 'WORKGROUP' smb: do_mount - [smb:///data; 1] res = -1, cancelled = 0, errno = [2] 'No such file or directory' smb: do_mount - (errno != EPERM && errno != EACCES), cancelled = 0, breaking smb: send_reply(0x5645821c1180), failed=1 (Failed to mount Windows share: No such file or directory) ** Config B *** smb: g_vfs_backend_smb_init: default workgroup = 'NULL' smb: Added new job source 0x559836d1d080 (GVfsBackendSmb) smb: Queued new job 0x559836d1e990 (GVfsJobMount) smb: do_mount - URI = smb:///data smb: do_mount - try #0 smb: auth_callback - kerberos pass smb: auth_callback - out: last_user = '', last_domain = 'WORKGROUP' smb: do_mount - [smb:///data; 0] res = -1, cancelled = 0, errno = [1] 'Operation not permitted' smb: do_mount - enabling NTLMSSP fallback smb: do_mount - try #1 smb: auth_callback - ccache pass smb: auth_callback - out: last_user = '', last_domain = 'WORKGROUP' smb: do_mount - [smb:///data; 1] res = -1, cancelled = 0, errno = [1] 'Operation not permitted' smb: do_mount - try #2 smb: auth_callback - normal pass smb: auth_callback - asking for password... smb: auth_callback - out: last_user = '', last_domain = 'WORKGROUP' smb: do_mount - [smb:///data; 2] res = -1, cancelled = 0, errno = [1] 'Operation not permitted' smb: do_mount - try #3 smb: auth_callback - normal pass smb: auth_callback - asking for password... *** system * Description:Ubuntu 20.04.2 LTS Release:20.04 samba: Installed: 2:4.11.6+dfsg-0ubuntu1.6 Candidate: 2:4.11.6+dfsg-0ubuntu1.6 Version table: *** 2:4.11.6+dfsg-0ubuntu1.6 500 500 http://pl.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 2:4.11.6+dfsg-0ubuntu1 500 500 http://pl.archive.ubuntu.com/ubuntu focal/main amd64 Packages ** Affects: samba (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/1917364 Title: gio mount does not mount Time Capsule SMB1 share, reports errors in a misleading way To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1917364/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904590] Re: Virtualbox does not work on 20.04-edge kernel due to DKMS build failure
*** This bug is a duplicate of bug 1901904 *** https://bugs.launchpad.net/bugs/1901904 About: > Still the same issue with virtualbox 6.1.10-dfsg-1~ubuntu1.20.04.1 on kernel 5.8.0.36.40~20.04.21 That is because the support for kernel 5.8 line was added in VirtualBox 6.1.14. I'm not sure why would anyone expect th As the version in official Ubuntu repos is now 6.1.16-dfsg-6~ubuntu1.20.04.1 I've reverted to using official Ubuntu repos, and everything works all right. I think this bug can be basically marked as resolved. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904590 Title: Virtualbox does not work on 20.04-edge kernel due to DKMS build failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1904590/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904590] Re: Virtualbox does not work on 20.04-edge kernel due to DKMS build failure
FYI, from the Virtualbox changelog at https://www.virtualbox.org/wiki/Changelog-6.1: > VirtualBox 6.1.14: > ... > Linux host and guest: Linux kernel version 5.8 support Therefore, it should be fixed after the VirtualBox package on Ubuntu 20.04 gets updated. After running into the same issue as you, I installed VirtualBox 6.1.16 from the Virtualbox.org contrib PPA, and the VMs run alright on my fresh 5.8.0-33-lowlatency kernel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904590 Title: Virtualbox does not work on 20.04-edge kernel due to DKMS build failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1904590/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding
I also can't get the hardware acceleration on Youtube.
With Netflix I do get DecryptingVideoDecoder.
Also there is no "Hardware-accelerated video decode" in flags.
Chromium snap version 84.0.4147.135 from candidate/vaapi channel.
$ vainfo
libva info: VA-API version 1.7.0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/radeonsi_drv_video.so
libva info: Found init function __vaDriverInit_1_7
libva info: va_openDriver() returns 0
vainfo: VA-API version: 1.7 (libva 2.6.0)
vainfo: Driver version: Mesa Gallium driver 20.0.8 for AMD Radeon RX 5600 XT
(NAVI10, DRM 3.38.0, 5.8.3-xanmod1, LLVM 10.0.0)
vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple: VAEntrypointVLD
VAProfileMPEG2Main : VAEntrypointVLD
VAProfileVC1Simple : VAEntrypointVLD
VAProfileVC1Main: VAEntrypointVLD
VAProfileVC1Advanced: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
VAProfileH264Main : VAEntrypointVLD
VAProfileH264Main : VAEntrypointEncSlice
VAProfileH264High : VAEntrypointVLD
VAProfileH264High : VAEntrypointEncSlice
VAProfileHEVCMain : VAEntrypointVLD
VAProfileHEVCMain : VAEntrypointEncSlice
VAProfileHEVCMain10 : VAEntrypointVLD
VAProfileJPEGBaseline : VAEntrypointVLD
VAProfileVP9Profile0: VAEntrypointVLD
VAProfileVP9Profile2: VAEntrypointVLD
VAProfileNone : VAEntrypointVideoProc
chrome://media-internals/
render_id: 9
player_id: 24
origin_url: https://www.youtube.com/
kFrameUrl: https://www.youtube.com/watch?v=LXb3EKWsInQ
kFrameTitle: COSTA RICA IN 4K 60fps HDR (ULTRA HD) - YouTube
url: blob:https://www.youtube.com/61c207f8-ceac-4af4-ab57-2e6c0526d53b
info: Effective playback rate changed from 0 to 1
pipeline_state: kPlaying
kAudioTracks: [object Object]
duration: 313.840907
kVideoTracks: [object Object]
kIsAudioDecryptingDemuxerStream: false
kAudioDecoderName: FFmpegAudioDecoder
kIsPlatformAudioDecoder: false
error:
{"causes":[{"causes":[],"data":{"codec":"h264"},"stack":[{"file":"../../media/filters/dav1d_video_decoder.cc","line":165}],"status_code":260,"status_message":""}],"data":{"Decoder
name":"Dav1dVideoDecoder"},"stack":[{"file":"../../media/filters/decoder_selector.cc","line":172}],"status_code":265,"status_message":""}
kIsVideoDecryptingDemuxerStream: false
kVideoDecoderName: FFmpegVideoDecoder
kIsPlatformVideoDecoder: false
audio_buffering_state: [object Object]
dimensions: 1920x1080
kResolution: 1920x1080
video_buffering_state: [object Object]
pipeline_buffering_state: [object Object]
event: kPlay
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1816497
Title:
[snap] vaapi chromium no video hardware decoding
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892085] Re: Wrong cursor theme (Adwaita) for cursors set by CSS, like cursor:wait and cursor:grab
The Opera snap has exactly the same problem. Firefox snap shows the correct cursors. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892085 Title: Wrong cursor theme (Adwaita) for cursors set by CSS, like cursor:wait and cursor:grab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1892085/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864365] Re: [snap] Dialog font missing
Also the Opera snap has the exact same problem. So this definitely isn't resolved. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864365 Title: [snap] Dialog font missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1864365/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864365] Re: [snap] Dialog font missing
So today the problem returned. I'm using the beta channel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864365 Title: [snap] Dialog font missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1864365/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864365] Re: [snap] Dialog font missing
I recently added nerd-fonts to my system. I placed them in ~/.local/share/fonts directory. https://github.com/ryanoasis/nerd-fonts And now I have this bug. I removed that directory and copied all those fonts to ~/.fonts and the bug is gone. I'm not sure if some programs need the fonts to be in ~/.local/share/fonts directory. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864365 Title: [snap] Dialog font missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1864365/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867402] Re: [snap] Icons in file picker are corrupted
I have two themes connected: content[icon-themes] chromium:icon-themes gtk-common-themes:icon-themes - content[icon-themes] chromium:icon-themes qogir-themes:icon-themesmanual And only if I choose Yaru or one of the Qogir variants I don't get the corrupted icons in file picker. Choosing Adwaita, Dmz-white, Dmz-black, Highcontrast or any other icon theme results in corrupted icons. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867402 Title: [snap] Icons in file picker are corrupted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1867402/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776873] Re: Whitelisted allowedURLschemes breaks some desktop apps
Magnet links are working. I just tried opening it in Chromium snap and I got the "xdg-open" prompt and than a window with selection between qBittorrent and Transmission. I selected qBittorrent and it opened the magnet link. $ snap version snap2.45 snapd 2.45 series 16 ubuntu 20.04 kernel 5.7.0-xanmod1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776873 Title: Whitelisted allowedURLschemes breaks some desktop apps To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1776873/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877727] Re: Nvidia dGPU active despite prime-select set to Intel card
- Install WITH "Install third-party software for graphics and WiFi hardware and additional media formats" 1. Open "Nvidia X Server Setting" 2. Changing card in "Prime Profiles" from "NVIDIA (Performance Mode)" to "Intel (Power Saving Mode)" 3. Reboot 4. After start Nvidia card STILL active (check by led light - orange - nvidia ACTIVE and more power consumption) - Install WITHOUT "Install third-party software for graphics and WiFi hardware and additional media formats" 1. Open "Additional drivers" 2. Click "Using NVIDIA driver metapackage from nvidia-driver-440 (proprietary, tested)" 3. Apply Changes, password 4. Reboot 5. Open "Nvidia X Server Setting" 6. Changing card in "Prime Profiles" from "NVIDIA (Performance Mode)" to "Intel (Power Saving Mode)" 7. Reboot 8. After start Nvidia card NOT active (check by led light - blue - nvidia INACTIVE and less power consumption) If any more info need please ask. I have separate partition on disk if there is need to do any test with newly installed Ubuntu. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877727 Title: Nvidia dGPU active despite prime-select set to Intel card To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1877727/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1765363] Re: prime-select intel is not powering off the nvidia card
I also have this bug. It seems that problem is on Ubuntu installer please check that comment: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1877727/comments/7 I reinstall Ubuntu and NOT checked to install proprietary driver. After Ubuntu install, I install Nvidia driver via the Additional Drivers application. After reboot, change graphic card to Intel and next reboot everything works great. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1765363 Title: prime-select intel is not powering off the nvidia card To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1765363/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877727] Re: Nvidia dGPU active despite prime-select set to Intel card
I also confirm that clean install of Ubuntu without option to install proprietary driver works OK. This is problem with installer option. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877727 Title: Nvidia dGPU active despite prime-select set to Intel card To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1877727/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877727] [NEW] Nvidia dGPU active despite prime-select set to Intel card
Public bug reported: After fresh installation of Ubuntu 20.04 I changed used card to Intel GPU with command "sudo prime-select intel". After reboot Intel card is used to display, but dGPU is still active (more heat and power consumption, this laptop also has led that indicate dGPU activation). In Ubuntu 19.04 which I used till today, after change to iGPU, laptop use iGPU and dGPU is in inactive state. I have MSI PE70 7RD laptop with Intel 7700HQ processor and NVIDIA 1050 GPU. I found similar problem on net, but without solution. https://askubuntu.com/questions/1232461/ubuntu-20-04-dgpu-is-always-on Workaround that I found is use "powertop" and in Tunables card activate power saving for dGPU card "Runtime PM for PCI Device NVIDIA Corporation GP107M [GeForce GTX 1050 Mobile]", but I think it should work without such changes every reboot. Description:Ubuntu 20.04 LTS Release:20.04 nvidia-prime: Installed: 0.8.14 Candidate: 0.8.14 Version table: *** 0.8.14 500 500 http://pl.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://pl.archive.ubuntu.com/ubuntu focal/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nvidia-prime 0.8.14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat May 9 11:38:41 2020 Dependencies: InstallationDate: Installed on 2020-05-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: nvidia-prime UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-prime (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/1877727 Title: Nvidia dGPU active despite prime-select set to Intel card To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1877727/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798450] Re: [snap] File dialogs show snap's home directory instead of user's
Correction it seems that you can select an image from your Images folder but it doesn't actually get uploaded. I'm trying again to upload the image. Maybe this time it will work. ** Attachment added: "chromium file picker 24.04.2020.png" https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1798450/+attachment/5358733/+files/chromium%20file%20picker%2024.04.2020.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1798450 Title: [snap] File dialogs show snap's home directory instead of user's To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1798450/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798450] Re: [snap] File dialogs show snap's home directory instead of user's
So the issue is somewhat still present with newest snap system. I'm on 20.04 LTS. The file picker in Chromium opens up in the snap directory but you can easily switch to your home directory. I've uploaded this screenshot using Chromium snap. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1798450 Title: [snap] File dialogs show snap's home directory instead of user's To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1798450/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869564] Re: package openbox 3.6.1-1ubuntu2.1 failed to install/upgrade: paket çok tutarsız bir durumda; yapılandırmaya teşebbüs etmeden önce paketi yeniden kurmanız daha iyi olur
** Changed in: openbox (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869564 Title: package openbox 3.6.1-1ubuntu2.1 failed to install/upgrade: paket çok tutarsız bir durumda; yapılandırmaya teşebbüs etmeden önce paketi yeniden kurmanız daha iyi olur To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openbox/+bug/1869564/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867502] Re: Netboot Loading libc6-udeb failed for unknown reasons (focal)
UAI customer has reported this issue under SF#00270036. It's easily reproducible with Focal's ubuntu-installer. http://archive.ubuntu.com/ubuntu/dists/focal/main/installer- amd64/current/images/netboot/ubuntu-installer/amd64/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867502 Title: Netboot Loading libc6-udeb failed for unknown reasons (focal) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1867502/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802407] Re: ssl_ca not supported
Hi Alex Can we get this fix backported to Bionic ? I have UAI customer that is affected by this bug. I've tested provided patch on Bionic and it fixes this issue. Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802407 Title: ssl_ca not supported To manage notifications about this bug go to: https://bugs.launchpad.net/charm-glance-simplestreams-sync/+bug/1802407/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1816473] Re: obamenu depends on python2
I will push fix for that to Debian repo at this week. > Also reading /etc/xdg/openbox/menu.xml There's a comment above the call to obconf that says "This requires the presence of the 'openbox- menu' package to work." Needless to say, that doesn't help XD ahrrr my bad -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1816473 Title: obamenu depends on python2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openbox/+bug/1816473/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866089] [NEW] Missing sound icon/ indicator
Public bug reported: There is no sound icon on the top panel, but there seems to be a (small) placeholder for it since it does change the volume when I scroll over the space between the network and battery icons. It's not present in either stock ubuntu and gnome-session or the login screen, tried booting with headphones plugged in with same result. Wasn't there when booted from the iso as well. Stock install Ubuntu 20.04 from a daily iso gnome-shell 3.35.91-1ubuntu2 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 4 15:10:26 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2020-03-04 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200303) RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug focal ** Attachment added: "screenshot.png" https://bugs.launchpad.net/bugs/1866089/+attachment/5333549/+files/screenshot.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866089 Title: Missing sound icon/ indicator To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834250] Re: update-grub complains about non-existent drives (due to cardreader)
I'm running 19.10 x64 (up to date as of today), LVM setup. Originally installed 19.04 and upgraded. This affects me too. Or, affected rather, because after following advice from comment #9 above it seems fixed. Details follow. ``` $ sudo update-grub2 Sourcing file `/etc/default/grub' Sourcing file `/etc/default/grub.d/init-select.cfg' Generating grub configuration file ... /dev/sda: open failed: No medium found /dev/sda: open failed: No medium found /dev/sda: open failed: No medium found /dev/sda: open failed: No medium found /dev/sda: open failed: No medium found /dev/sda: open failed: No medium found /dev/sda: open failed: No medium found /dev/sda: open failed: No medium found /dev/sda: open failed: No medium found /dev/sda: open failed: No medium found Found linux image: /boot/vmlinuz-5.3.0-29-generic Found initrd image: /boot/initrd.img-5.3.0-29-generic Found linux image: /boot/vmlinuz-5.3.0-26-generic Found initrd image: /boot/initrd.img-5.3.0-26-generic /dev/sda: open failed: No medium found /dev/sda: open failed: No medium found /dev/sda: open failed: No medium found ``` It goes on, but I'm skipping it. ``` $ lsblk nvme0n1 259:00 931.5G 0 disk ├─nvme0n1p1 259:10 512M 0 part /boot/efi ├─nvme0n1p2 259:20 732M 0 part /boot └─nvme0n1p3 259:30 930.3G 0 part └─nvme0n1p3_crypt 253:00 930.3G 0 crypt ├─ubuntu--vg-root 253:10 929.3G 0 lvm / └─ubuntu--vg-swap_1 253:20 976M 0 lvm [SWAP] ``` Above I'm skipping bunch of loop## from output of lsblk. The Ubuntu "Disks" app identified the /dev/sda as "Generic- SD/MMC". It seems it's a built-in card reader of my ThinkPad. I decided to follow comment #9 above to filter out that device from LVM. And, advice from comment #9 fixed the issue! Thanks a lot Zer00Cool! What I did exactly is: 1. grep for "global_filter" in lvm.conf - that file is really long... ``` $ grep -Fn "global_filter" /etc/lvm/lvm.conf 142:# Configuration option devices/global_filter. 146:# Use global_filter to hide devices from these LVM system components. 148:# global_filter are not opened by LVM. 150:# global_filter = [ "a|.*/|" ] ``` 2. After the commented out "global_filter" setting (line 150 in my case), I added the following: ``` global_filter = [ "r|/dev/sda|" ] ``` -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1834250 Title: update-grub complains about non-existent drives (due to cardreader) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1834250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1497727] Re: evince-thumbnailer DOSes rsyslogd
I experienced the same bug with syslog flooded. It seems that it happens when PDF or SVG documents have embedded LaTeX font (often cmr10 but I bet that with others it would be the same) gnome has problems with generating thumbnails. In my case it is looking for the right TFM file in texlive font directory: gnome-session[3640]: page: Warning: font `cmr10' not found, trying metric files instead gnome-session[3640]: page: Error: /usr/share/texlive/texmf-dist/fonts/tfm/public/cm/cmr10.tfm: File corrupted, or not a TFM file and it finds it corrupted and retries filling the log. When I remove the "corrupted" file gnome tries to regenerate it but it finds the folder read-only. gnome-session[3640]: kpathsea: Running mkofm cmr10 gnome-session[3640]: mkofm: Permission denied I solved the problem by regenerating TFM manually: mktextfm cmr10 and substituting the TFM file in texlive. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1497727 Title: evince-thumbnailer DOSes rsyslogd To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1497727/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848892] Re: "error: Unknown TPM error." after upgrading to grub 2.04
I have the same issue after upgrading to Kubuntu 19.10. I worked around it by disabling secure boot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848892 Title: "error: Unknown TPM error." after upgrading to grub 2.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1848892/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1740736] Re: The it87.ko driver is too old and does not support newer chipsets (such as Z370).
IT8686E does not work on X470 motherboard and upstream 5.2.15 kernel. There has been no upstream movement around `linux/drivers/hwmon/it87.c` since 2 years. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1740736 Title: The it87.ko driver is too old and does not support newer chipsets (such as Z370). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1740736/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842169] [NEW] AHCI Host Controller Runtime Power Management not set to powersave mode "auto" despite set AHCI_RUNTIME_PM_ON_BAT to "auto"
Public bug reported:
Description:Ubuntu 19.04
Release:19.04
Package:
tlp:
Installed: 1.1-2ubuntu1
Candidate: 1.1-2ubuntu1
Version table:
*** 1.1-2ubuntu1 500
500 http://pl.archive.ubuntu.com/ubuntu disco/universe amd64 Packages
500 http://pl.archive.ubuntu.com/ubuntu disco/universe i386 Packages
100 /var/lib/dpkg/status
This is small bug that I found when checking max possible power saving
of my laptop.
I have set AHCI_RUNTIME_PM_ON_BAT to auto on file /etc/default/tlp:
# Runtime Power Management for AHCI host and disks devices:
# on=disable, auto=enable.
# EXPERIMENTAL ** WARNING: auto will most likely cause system lockups/data loss.
AHCI_RUNTIME_PM_ON_AC=auto
AHCI_RUNTIME_PM_ON_BAT=auto
tlp-stat -T (TLP debug log) says that enabled:
sie 31 09:01:38 mateo-PE70-7RD tlp[1694]: set_ahci_runtime_pm(0).auto:
host=/sys/bus/pci/devices/:00:17.0/ata1
sie 31 09:01:38 mateo-PE70-7RD tlp[1695]: set_ahci_runtime_pm(0).auto:
host=/sys/bus/pci/devices/:00:17.0/ata2
sie 31 09:01:38 mateo-PE70-7RD tlp[1696]: set_ahci_runtime_pm(0).auto:
host=/sys/bus/pci/devices/:00:17.0/ata3
sie 31 09:01:38 mateo-PE70-7RD tlp[1697]: set_ahci_runtime_pm(0).auto:
host=/sys/bus/pci/devices/:00:17.0/ata4
but tlp-stat says different thing:
+++ AHCI Host Controller Runtime Power Management
/sys/bus/pci/devices/:00:17.0/ata1/power/control = on
/sys/bus/pci/devices/:00:17.0/ata2/power/control = on
/sys/bus/pci/devices/:00:17.0/ata3/power/control = on
/sys/bus/pci/devices/:00:17.0/ata4/power/control = on
I have found that in file "/usr/share/tlp/tlp-functions" in line 1491 is:
{ printf '%s\n' $control $control > ${device}/power/control; } 2>
/dev/null
what I think could be a problem. After change to this it starts to work:
{ printf '%s\n' $control > ${device}/power/control; } 2> /dev/null
Could you please check this? It seems Ubuntu 18.04 could have the same
problem (the same package).
Best Regards
Mateusz
** Affects: tlp (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/1842169
Title:
AHCI Host Controller Runtime Power Management not set to powersave
mode "auto" despite set AHCI_RUNTIME_PM_ON_BAT to "auto"
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tlp/+bug/1842169/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771836] Re: landscape-client fails when doing system upgrade
*** This bug is a duplicate of bug 1728681 *** https://bugs.launchpad.net/bugs/1728681 Can you confirm if data_path is a new parameter or was it present in default config in all previous versions of landscape-client ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1771836 Title: landscape-client fails when doing system upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1771836/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771836] Re: landscape-client fails when doing system upgrade
Missing data_path is causing this. Following resolves issue. 1. echo data_path = /var/lib/landscape/client >> /etc/landscape/client.conf 2. apt purge landscape-client 3. apt install landscape-client -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1771836 Title: landscape-client fails when doing system upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1771836/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826184] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1826184/+attachment/5258558/+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/1826184 Title: Closing tab via shortcut causes crash To manage notifications about this bug go to: https://bugs.launchpad.net/guake/+bug/1826184/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826184] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1826184/+attachment/5258556/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826184 Title: Closing tab via shortcut causes crash To manage notifications about this bug go to: https://bugs.launchpad.net/guake/+bug/1826184/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826184] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1826184/+attachment/5258557/+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/1826184 Title: Closing tab via shortcut causes crash To manage notifications about this bug go to: https://bugs.launchpad.net/guake/+bug/1826184/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826184] [NEW] Closing tab via shortcut causes crash
Public bug reported: Upstream bug: https://github.com/Guake/guake/issues/1478 Said to be fixed in 3.5.0 release. Repro: 1. Open new tab (Ctrl+Shift+T) 2. Close tab (Ctrl+Shift+W) Tab does not close and crash report is generated. The error: TypeError: delete_page_current() takes from 1 to 2 positional arguments but 5 were given --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-04-18 (5 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) NonfreeKernelModules: nvidia_modeset nvidia Package: guake 3.4.0-1 PackageArchitecture: all ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True ** Affects: guake Importance: Unknown Status: Unknown ** Affects: guake (Ubuntu) Importance: Undecided Status: New ** Tags: apport-collected disco ** Bug watch added: github.com/Guake/guake/issues #1478 https://github.com/Guake/guake/issues/1478 ** Also affects: guake via https://github.com/Guake/guake/issues/1478 Importance: Unknown Status: Unknown ** Description changed: Upstream bug: https://github.com/Guake/guake/issues/1478 Said to be fixed in 3.5.0 release. Repro: 1. Open new tab (Ctrl+Shift+T) 2. Close tab (Ctrl+Shift+W) Tab does not close and crash report is generated. + + The error: + TypeError: delete_page_current() takes from 1 to 2 positional arguments but 5 were given ** Tags added: apport-collected disco ** Description changed: Upstream bug: https://github.com/Guake/guake/issues/1478 Said to be fixed in 3.5.0 release. Repro: 1. Open new tab (Ctrl+Shift+T) 2. Close tab (Ctrl+Shift+W) Tab does not close and crash report is generated. The error: TypeError: delete_page_current() takes from 1 to 2 positional arguments but 5 were given + --- + ProblemType: Bug + ApportVersion: 2.20.10-0ubuntu27 + Architecture: amd64 + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 19.04 + InstallationDate: Installed on 2019-04-18 (5 days ago) + InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) + NonfreeKernelModules: nvidia_modeset nvidia + Package: guake 3.4.0-1 + PackageArchitecture: all + ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 + Tags: disco + Uname: Linux 5.0.0-13-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip docker libvirt lpadmin plugdev sambashare sudo + _MarkForUpload: True -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826184 Title: Closing tab via shortcut causes crash To manage notifications about this bug go to: https://bugs.launchpad.net/guake/+bug/1826184/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826033] [NEW] package systemd 239-7ubuntu10.13 failed to install/upgrade: installed systemd package post-installation script subprocess returned error exit status 1
Public bug reported: During upgrade 18.04 -> 19.04 in chroot. ProblemType: Package DistroRelease: Ubuntu 18.10 Package: systemd 239-7ubuntu10.13 ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18 Uname: Linux 4.15.0-47-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 Date: Tue Apr 23 17:04:51 2019 Df: Filesystem 1K-blocksUsed Available Use% Mounted on /dev/mapper/vg_raid10_bitmap-root_ubuntu_new 20971520 4667480 13764520 26% / udev 1961312 0 1961312 0% /dev tmpfs 4035047208396296 2% /run ErrorMessage: installed systemd package post-installation script subprocess returned error exit status 1 Lspci: Error: [Errno 2] No such file or directory: 'lspci': 'lspci' Lsusb: Error: [Errno 2] No such file or directory: 'lsusb': 'lsusb' MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-47-generic root=/dev/mapper/vg_raid10_bitmap-root ro ipv6.disable=1 consoleblank=0 net.ifnames=0 biosdevname=0 Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3 RelatedPackageVersions: dpkg 1.19.0.5ubuntu5 apt 1.6.10 SourcePackage: systemd SystemdFailedUnits: Running in chroot, ignoring request: status Title: package systemd 239-7ubuntu10.13 failed to install/upgrade: installed systemd package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to cosmic on 2019-04-23 (0 days ago) dmi.bios.date: 02/12/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P4.70 dmi.board.name: A320M Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP4.70:bd02/12/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnA320MPro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. mtime.conffile..etc.systemd.timesyncd.conf: 2019-01-07T16:19:47.527584 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package cosmic 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/1826033 Title: package systemd 239-7ubuntu10.13 failed to install/upgrade: installed systemd package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1826033/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1764137] Re: [bionic][beta][nvidia] gnome-shell high CPU utilization when using Nvidia driver
It was long time ago but IIRC after upgrading from Ubuntu 17.10 to 18.04 GDM would try to start on Wayland. With proprietary Nvidia driver it would then fallback to software rendering haence the CPU usage. Disabling Wayland in /etc/gdm/custom.conf or doing clean install fixes the issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1764137 Title: [bionic][beta][nvidia] gnome-shell high CPU utilization when using Nvidia driver To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1764137/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1261175] Re: [wishlist] F2FS missing in Ubiquity "Use as" partition option
> Any such d-i component is going to have to warn that the partition on which /boot resides cannot be f2fs, since grub does not support booting from f2fs yet. Next GRUB 2 release will include F2FS support. The change is so simple it could be easily backported: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1817310 What remains is creating partman-f2fs and moving f2fs-* packages from universe to main. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1261175 Title: [wishlist] F2FS missing in Ubiquity "Use as" partition option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1261175/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1734520] Re: Enable atomic write support for f2fs
** Tags added: f2fs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1734520 Title: Enable atomic write support for f2fs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sqlite3/+bug/1734520/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817310] [NEW] Backport F2FS support
Public bug reported: It's single commit that doesn't affect other filesystems: https://git.savannah.gnu.org/cgit/grub.git/commit/?id=71f9e4ac44142af52c3fc1860436cf9e432bf764 It'll enable users to boot from F2FS partitions without requiring separate /boot. Additionally it should simplify F2FS support in the installer https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1261175 ** Affects: grub2 (Ubuntu) Importance: Undecided Status: New ** Tags: f2fs ** Tags added: f2fs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817310 Title: Backport F2FS support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1817310/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1572908] Re: sssd-ad pam_sss(cron:account): Access denied for user
As johannes-martin pointed out default value for ad_gpo_map_batch doesn't work on Ubuntu Xenial and newer because cron service runs as cron not crond. Solution to this issue would be listing cron as PAM service name and restarting sssd. ad_gpo_map_batch = +cron -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1572908 Title: sssd-ad pam_sss(cron:account): Access denied for user To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1572908/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1808980] Re: Ubuntu/Debian Firefox packages are built without SIMD
** Changed in: firefox (Debian) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1808980 Title: Ubuntu/Debian Firefox packages are built without SIMD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1808980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1710858] Re: totem crashed with SIGSEGV in in __GI_____strtoul_l_internal() from __GI___strtoul_l() from g_ascii_strtoull() from _cogl_gpu_info_parse_version_string() from check_mesa_driver_packa
Fixied in Bionic, Artful is EOL. ** Changed in: totem (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1710858 Title: totem crashed with SIGSEGV in in __GI_strtoul_l_internal() from __GI___strtoul_l() from g_ascii_strtoull() from _cogl_gpu_info_parse_version_string() from check_mesa_driver_package() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1710858/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1808980] Re: Ubuntu/Debian Firefox packages are built without SIMD
** Also affects: firefox (Debian) 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/1808980 Title: Ubuntu/Debian Firefox packages are built without SIMD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1808980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1808980] [NEW] Ubuntu/Debian Firefox packages are built without SIMD
Public bug reported: Official Firefox releases and other distributions packages are built with `--enable-rust-simd` to improve performance. Official build option: https://github.com/mozilla/gecko- dev/blob/13788edbabb04d004e4a1ceff41d4de68a8320a2/build/mozconfig.rust#L12 `--enable-rust-simd` enables runtime detection of CPU features such as SSE and AVX in Rust written components. To check if Firefox is built with simd open `about:buildconfig` and look for `--enable-rust-simd`. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Description changed: Official Firefox releases and other distributions packages are built - with `--enable-rust-simd` to improve performance. + with `--enable-rust-simd` to improve performance. Official build + option: https://github.com/mozilla/gecko- + dev/blob/13788edbabb04d004e4a1ceff41d4de68a8320a2/build/mozconfig.rust#L12 `--enable-rust-simd` enables runtime detection of CPU features such as SSE and AVX in Rust written components. To check if Firefox is built with simd open `about:buildconfig` and look for `--enable-rust-simd`. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1808980 Title: Ubuntu/Debian Firefox packages are built without SIMD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1808980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1805898] [NEW] package nvidia-340 (not installed) failed to install/upgrade: próba nadpisania "/lib/udev/rules.d/71-nvidia.rules", który istnieje także w pakiecie nvidia-kernel-common-390 390.87-
Public bug reported: I have Nvidia card Asus strix 950 ti i instal this driver and my system dosne't work i mast reinstal gdm3 nad gdm3 ubuntu-desktop ProblemType: Package DistroRelease: Ubuntu 18.04 Package: nvidia-340 (not installed) ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Uname: Linux 4.15.0-39-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Thu Nov 29 20:42:47 2018 ErrorMessage: próba nadpisania "/lib/udev/rules.d/71-nvidia.rules", który istnieje także w pakiecie nvidia-kernel-common-390 390.87-0ubuntu0~gpu18.04.1 InstallationDate: Installed on 2018-11-27 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: nvidia-graphics-drivers-340 Title: package nvidia-340 (not installed) failed to install/upgrade: próba nadpisania "/lib/udev/rules.d/71-nvidia.rules", który istnieje także w pakiecie nvidia-kernel-common-390 390.87-0ubuntu0~gpu18.04.1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-340 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1805898 Title: package nvidia-340 (not installed) failed to install/upgrade: próba nadpisania "/lib/udev/rules.d/71-nvidia.rules", który istnieje także w pakiecie nvidia-kernel-common-390 390.87-0ubuntu0~gpu18.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1805898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798790] Re: Ubuntu 18.10 login screen never appears when using the Nvidia driver
Another workaround is adding `nvidia-drm.modeset=1` to the kernel command line. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1798790 Title: Ubuntu 18.10 login screen never appears when using the Nvidia driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1798790/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1799305] Re: No desktop after reboot when using nvidia graphics on 18.10
Possibly duplicate of https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1798790 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799305 Title: No desktop after reboot when using nvidia graphics on 18.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1799305/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power
Tested with MSI PE70 7RD ( Intel i7-7700HQ and GeForce GTX 1050 ) and Ubuntu 18.04 fresh install. Proposed Packages install fine. Change of graphic with PRIME and log out/in working fast and without problem. Nvidia driver is not loaded in Power Saving Mode and power is OK ~10W idle. Led indicates that the nvidia GPU is off. Suspend and resume also works. Thanks for the work. ** Attachment added: "gpu-manager.log" https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1778011/+attachment/5197245/+files/gpu-manager.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1778011 Title: SRU: PRIME Power Saving mode draws too much power To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1778011/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1793487] Re: bzr invocation fails after today bionic upgrade
False alarm, after restarting, bzr/ qbzr works as expected. ** Changed in: bzr (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1793487 Title: bzr invocation fails after today bionic upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bzr/+bug/1793487/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1793487] [NEW] bzr invocation fails after today bionic upgrade
Public bug reported: $ BZR_DEBUG=1 bzr Traceback (most recent call last): File "/usr/bin/bzr", line 109, in import bzrlib.commands File "/usr/lib/python2.7/dist-packages/bzrlib/commands.py", line 49, in from bzrlib.hooks import Hooks File "/usr/lib/python2.7/dist-packages/bzrlib/hooks.py", line 95, in known_hooks.register_lazy_hook(_hook_module, _hook_attribute, _hook_class) File "/usr/lib/python2.7/dist-packages/bzrlib/hooks.py", line 46, in register_lazy_hook self.register_lazy((hook_module_name, hook_member_name), AttributeError: 'KnownHooksRegistry' object has no attribute 'register_lazy' ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bzr 2.7.0+bzr6622-10 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CurrentDesktop: KDE Date: Thu Sep 20 11:26:24 2018 PackageArchitecture: all SourcePackage: bzr UpgradeStatus: Upgraded to bionic on 2018-09-04 (15 days ago) ** Affects: bzr (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic 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/1793487 Title: bzr invocation fails after today bionic upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bzr/+bug/1793487/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1791542] Re: package libglvnd-dev 1.0.0-2ubuntu2.1 failed to upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so', which is also in package nvidia-340 340.107-0ubuntu0~gpu18.0
** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1791542 Title: package libglvnd-dev 1.0.0-2ubuntu2.1 failed to upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so', which is also in package nvidia-340 340.107-0ubuntu0~gpu18.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1791542/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1773802] [NEW] program crashes with "Segmentation Fault" in multiple situations because of missing time.h header
Public bug reported: Steps to reproduce: $ printf "GET https://ip.pr1v.net/ HTTP/1.0\r\n\r\n" | ./micro_proxy HTTP/1.0 400 Bad Request Server: micro_proxy Segmentation fault $ printf "GET http://incorrect.address.0/ HTTP/1.0\r\n\r\n" | ./micro_proxy HTTP/1.0 404 Not Found Server: micro_proxy Segmentation fault Fix: diff --git a/micro_proxy.c b/micro_proxy.c index 78e317f..3d6c144 100644 --- a/micro_proxy.c +++ b/micro_proxy.c @@ -38,6 +38,8 @@ #include #include #include +#include After fix: $ printf "GET http://incorrect.address.0/ HTTP/1.0\r\n\r\n" | ./micro_proxy HTTP/1.0 404 Not Found Server: micro_proxy Date: Mon, 28 May 2018 13:11:48 GMT Content-Type: text/html Connection: close 404 Not Found 404 Not Found Unknown host. http://www.acme.com/software/micro_proxy/";>micro_proxy $ printf "GET https://ip.pr1v.net/ HTTP/1.0\r\n\r\n" | ./micro_proxy HTTP/1.0 400 Bad Request Server: micro_proxy Date: Mon, 28 May 2018 13:12:02 GMT Content-Type: text/html Connection: close 400 Bad Request 400 Bad Request Unknown URL type. http://www.acme.com/software/micro_proxy/";>micro_proxy ** Affects: micro-proxy (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/1773802 Title: program crashes with "Segmentation Fault" in multiple situations because of missing time.h header To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/micro-proxy/+bug/1773802/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
