[Bug 1967490] Re: systemd: apcupsd daemon parent exits before the child creates the pid file
The apcupsd developers answered to my report on their mailing list. See https://sourceforge.net/p/apcupsd/mailman/apcupsd- users/thread/CAKb_4nSxZCH_cFqXhb3N3t8ArFN_tn7ZiTTR5MCqBREDDiSyuQ%40mail.gmail.com/#msg37639690 At present time the only workaround it seems to be recompiling adding the sleep() call. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967490 Title: systemd: apcupsd daemon parent exits before the child creates the pid file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apcupsd/+bug/1967490/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970191] [NEW] package linux-image-5.13.0-40-generic 5.13.0-40.45 failed to install/upgrade: installed linux-image-5.13.0-40-generic package post-installation script subprocess returned error exi
Public bug reported: I'm trying to update VirtualBox guest additions with "sh ./VBoxLinuxAdditions.run" ProblemType: Package DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-40-generic 5.13.0-40.45 ProcVersionSignature: Ubuntu 5.13.0-39.44-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu71.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: max1373 F pulseaudio CasperMD5CheckResult: pass Date: Mon Apr 25 11:19:46 2022 ErrorMessage: installed linux-image-5.13.0-40-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-01-03 (111 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) IwConfig: lono wireless extensions. enp0s3no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/12p, 480M MachineType: innotek GmbH VirtualBox ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-39-generic root=/dev/mapper/vgubuntu-root ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 3.9.4-1build1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc 2.04-1ubuntu47 RfKill: SourcePackage: linux Title: package linux-image-5.13.0-40-generic 5.13.0-40.45 failed to install/upgrade: installed linux-image-5.13.0-40-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-package impish need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970191 Title: package linux-image-5.13.0-40-generic 5.13.0-40.45 failed to install/upgrade: installed linux-image-5.13.0-40-generic package post- installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970191/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967490] Re: systemd: apcupsd daemon parent exits before the child creates the pid file
** Description changed: The apcupsd.service file in Ubuntu 20.04 LTS (amd64) includes the following lines: Type=forking PIDFile=/var/run/apcupsd.pid The systemd documentation (https://www.freedesktop.org/software/systemd/man/systemd.service.html), searching for "Type=forking", reports the following statement: [...] ... if the process decides to write a traditional PID file, systemd will be able to read the main PID from there. Please set PIDFile= accordingly. Note that the daemon should write that file before finishing with its initialization. Otherwise, systemd might try to read the file before it exists. [...] The issue is that, although the daemon is started and works correctly, the "systemctl status apcupsd.service" call always reports the following: systemd[1]: apcupsd.service: Can't open PID file /run/apcupsd.pid (yet?) after start: Operation not permitted This glitch is due to the fact that the parent process of the daemon exits before the child has written the PID file. - I proved this statement by recompiling apcupsd from source and inserting a "sleep(1)" before the "exit(0) /* parent exits */" call in apcupsd.c:daemon_start() function. + I proved this statement by recompiling apcupsd from source and inserting a "sleep(1)" before the "exit(0) /* parent exits */" call in the daemon_start() function (of apcupsd.c). It fixed the issue by keeping the parent alive for a while, giving the child enough time to call make_pid_file(). I know that sleep(1) is not a bugfix rather a test for verifying the root cause of the issue. I reported the issue to the apcupsd developers before filling this bug. Anyway although their mailing list is alive and kicking, they do not release a new version since 2016 so I am not so confident that they will fix their source (at least not soon). So could you please implement and apply a patch to the source that delays the exit of the parent (i.e. waiting for the PID file of the child to be created) in order to make apcupsd 100% compatible with systemd? ** Description changed: The apcupsd.service file in Ubuntu 20.04 LTS (amd64) includes the following lines: Type=forking PIDFile=/var/run/apcupsd.pid The systemd documentation (https://www.freedesktop.org/software/systemd/man/systemd.service.html), searching for "Type=forking", reports the following statement: [...] ... if the process decides to write a traditional PID file, systemd will be able to read the main PID from there. Please set PIDFile= accordingly. Note that the daemon should write that file before finishing with its initialization. Otherwise, systemd might try to read the file before it exists. [...] The issue is that, although the daemon is started and works correctly, the "systemctl status apcupsd.service" call always reports the following: systemd[1]: apcupsd.service: Can't open PID file /run/apcupsd.pid (yet?) after start: Operation not permitted This glitch is due to the fact that the parent process of the daemon exits before the child has written the PID file. I proved this statement by recompiling apcupsd from source and inserting a "sleep(1)" before the "exit(0) /* parent exits */" call in the daemon_start() function (of apcupsd.c). It fixed the issue by keeping the parent alive for a while, giving the child enough time to call make_pid_file(). I know that sleep(1) is not a bugfix rather a test for verifying the root cause of the issue. I reported the issue to the apcupsd developers before filling this bug. Anyway although their mailing list is alive and kicking, they do not release a new version since 2016 so I am not so confident that they will fix their source (at least not soon). So could you please implement and apply a patch to the source that delays the exit of the parent (i.e. waiting for the PID file of the - child to be created) in order to make apcupsd 100% compatible with - systemd? + child to be created) in order to make apcupsd 100% compliant to what + systemd expects? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967490 Title: systemd: apcupsd daemon parent exits before the child creates the pid file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apcupsd/+bug/1967490/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967490] [NEW] systemd: apcupsd daemon parent exits before the child creates the pid file
Public bug reported: The apcupsd.service file in Ubuntu 20.04 LTS (amd64) includes the following lines: Type=forking PIDFile=/var/run/apcupsd.pid The systemd documentation (https://www.freedesktop.org/software/systemd/man/systemd.service.html), searching for "Type=forking", reports the following statement: [...] ... if the process decides to write a traditional PID file, systemd will be able to read the main PID from there. Please set PIDFile= accordingly. Note that the daemon should write that file before finishing with its initialization. Otherwise, systemd might try to read the file before it exists. [...] The issue is that, although the daemon is started and works correctly, the "systemctl status apcupsd.service" call always reports the following: systemd[1]: apcupsd.service: Can't open PID file /run/apcupsd.pid (yet?) after start: Operation not permitted This glitch is due to the fact that the parent process of the daemon exits before the child has written the PID file. I proved this statement by recompiling apcupsd from source and inserting a "sleep(1)" before the "exit(0) /* parent exits */" call in apcupsd.c:daemon_start() function. It fixed the issue by keeping the parent alive for a while, giving the child enough time to call make_pid_file(). I know that sleep(1) is not a bugfix rather a test for verifying the root cause of the issue. I reported the issue to the apcupsd developers before filling this bug. Anyway although their mailing list is alive and kicking, they do not release a new version since 2016 so I am not so confident that they will fix their source (at least not soon). So could you please implement and apply a patch to the source that delays the exit of the parent (i.e. waiting for the PID file of the child to be created) in order to make apcupsd 100% compatible with systemd? ** Affects: apcupsd (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/1967490 Title: systemd: apcupsd daemon parent exits before the child creates the pid file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apcupsd/+bug/1967490/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956875] [NEW] [HDA-Intel - HD-Audio Generic, recording] Recording problem: Headset mic not detected
Public bug reported: In my laptop (Huawei MateBook 14 2020 AMD R5, Model KLVL-WFH9) there is a single 3.5mm jack port which allows audio input and output. I've got a headset with a single cable, sound can be heard very good, microphone is not detected. The disk runs Windows 10 in one partition and in the other one Ubuntu 20.04. I also had trouble with Windows in recognizing the headset's mic but now that has been solved. However, in Ubuntu it is only detected and "categorized" as Headphone. There is no way to use the microphone of the headset. I've tried to find some similar issues but nothing has helped me so far. Thanks in advance, Lorenzo ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.7.17-050717-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jan 9 17:51:26 2022 InstallationDate: Installed on 2021-03-29 (286 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:Generic_1 successful Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:Generic_1 failed Symptom_Type: Only some of inputs are working Title: [HDA-Intel - HD-Audio Generic, recording] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/14/2020 dmi.bios.vendor: HUAWEI dmi.bios.version: 1.06 dmi.board.asset.tag: N/A dmi.board.name: KLVL-WXX9-PCB dmi.board.vendor: HUAWEI dmi.board.version: M1130 dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: HUAWEI dmi.chassis.version: M1130 dmi.modalias: dmi:bvnHUAWEI:bvr1.06:bd09/14/2020:svnHUAWEI:pnKLVL-WXX9:pvrM1130:rvnHUAWEI:rnKLVL-WXX9-PCB:rvrM1130:cvnHUAWEI:ct10:cvrM1130: dmi.product.family: MateBook 14 dmi.product.name: KLVL-WXX9 dmi.product.sku: C100 dmi.product.version: M1130 dmi.sys.vendor: HUAWEI mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-01-06T13:57:39.54 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956875 Title: [HDA-Intel - HD-Audio Generic, recording] Recording problem: Headset mic not detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1956875/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1954342] Re: Client authentication error "Failed to convert SID ... to a PID"
I think I've found the problem:
Quoting from the last patch:
From: Ralph Boehme
Date: Fri, 8 Oct 2021 12:33:16 +0200
Subject: [PATCH 138/284] CVE-2020-25717: s3:auth: remove fallbacks in
smb_getpwnam()
So far we tried getpwnam("DOMAIN\account") first and
always did a fallback to getpwnam("account") completely
ignoring the domain part, this just causes problems
as we mix "DOMAIN1\account", "DOMAIN2\account",
and "account"!
As we require a running winbindd for domain member setups
we should no longer do a fallback to just "account" for
users served by winbindd!
For users of the local SAM don't use this code path,
as check_sam_security() doesn't call check_account().
The only case where smb_getpwnam("account") happens is
when map_username() via ("username map [script]") mapped
"DOMAIN\account" to something without '\', but that is
explicitly desired by the admin.
-- end quote ---
So I've configured the smb.conf with:
username map script = /export/sbin/remove_domain.pl
to strip the domain from the username
This is a very basic perl script ( DONT USE THIS )
#!/usr/bin/perl -w
$username=$ARGV[0];
chomp $username;
if ($username =~ /^LABTA\\([a-zA-Z0-9\-]+)$/ ){
$username = $1;
print "$username\n";
}
With this configuration the 4.7.6+dfsg~ubuntu-0ubuntu2.26 starts to work.
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-25717
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1954342
Title:
Client authentication error "Failed to convert SID ... to a PID"
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1954342/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948710] [NEW] Suspend issues with nvidia proprietary driver
Public bug reported: When I suspend my system, after the screen goes black, the desktop and the suspend login screen are briefly shown in succession, and only then the screen, power LED and fan turn off like normally. The timing of the brief "fake resume" is not consistent: sometimes it only shows the login screen, sometimes it stops the suspension until briefly after I login. When resuming after this has happened, the login screen appears as normal, but I have to wait for any internet connection to restart, and my second screen remains blacks despite it being detected and the display mode remaining on "join displays", until I change the display mode back and forth to fix it. These issues occur after switching to the nvidia-driver-470 driver on a fresh install of Ubuntu 21.10, but I have been experiencing at least the "fake-resume" since at least 20.10, without being able to find any solution. These issues persist (with slightly altered timing) if I switch to an older proprietary driver (I tried nvidia-driver-390 and nvidia- driver-460), but do not appear while using the nouveau driver. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 NonfreeKernelModules: 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..01.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 470.74 Mon Sep 13 23:09:15 UTC 2021 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-7ubuntu2) ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Permesso negato: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Oct 25 21:09:03 2021 DistUpgraded: Fresh install DistroCodename: impish DistroVariant: ubuntu DkmsStatus: nvidia, 470.74, 5.13.0-20-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated Graphics Controller [1043:177d] Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 850M] [1043:177d] InstallationDate: Installed on 2021-10-21 (3 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: ASUSTeK COMPUTER INC. N551JK ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic root=UUID=64128e5f-ba67-49c1-aa02-c19feef6be26 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/06/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N551JK.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N551JK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN551JK.203:bd10/06/2014:br4.6:svnASUSTeKCOMPUTERINC.:pnN551JK:pvr1.0:skuASUS-NotebookSKU:rvnASUSTeKCOMPUTERINC.:rnN551JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: N dmi.product.name: N551JK dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish nvidia suspend-resume ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1948710 Title: Suspend issues with nvidia proprietary driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1948710/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com
[Bug 1871011] Re: USB scanning broken on focal by ippusbxd (was: hpmud and ippusbxd conflict)
On a fully updated Ubuntu 20.04.3 LTS with kernel 5.11.0-37-generic #41~20.04.2-Ubuntu I'm experiencing the same issue with my HP OfficeJet 4657. [40248.522045] usb 1-9.4: new high-speed USB device number 17 using xhci_hcd [40248.652858] usb 1-9.4: New USB device found, idVendor=03f0, idProduct=d911, bcdDevice= 1.00 [40248.652864] usb 1-9.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [40248.652866] usb 1-9.4: Product: OfficeJet 4650 series [40248.652868] usb 1-9.4: Manufacturer: HP [40248.652870] usb 1-9.4: SerialNumber: TH76F4918Q0662 [40248.726281] usblp 1-9.4:1.1: usblp5: USB Bidirectional printer dev 17 if 1 alt 0 proto 2 vid 0x03F0 pid 0xD911 [40248.920575] usb 1-9.4: usbfs: process 75785 (ippusbxd) did not claim interface 0 before use [40248.944349] usblp5: removed The workaround has been to remove IPPUSBXD: sudo apt remove ippusbxd Now I can scan again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871011 Title: USB scanning broken on focal by ippusbxd (was: hpmud and ippusbxd conflict) To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/1871011/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927348] [NEW] package ubuntu-advantage-tools 27.0~16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: My PC doesn't work regularly, It crashes very frequently, by stopping the possibility tu use the PC cause of a block of the desktop. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: ubuntu-advantage-tools 27.0~16.04.1 ProcVersionSignature: Ubuntu 4.4.0-210.242-generic 4.4.262 Uname: Linux 4.4.0-210-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.30 Architecture: amd64 Date: Thu May 6 11:07:12 2021 DpkgHistoryLog: Start-Date: 2021-05-06 11:06:34 Commandline: aptdaemon role='role-commit-packages' sender=':1.166' Install: python3-distro-info:amd64 (0.14ubuntu0.2, automatic), distro-info:amd64 (0.14ubuntu0.2, automatic), python3-yaml:amd64 (3.11-3build1, automatic), libzstd1:amd64 (1.3.1+dfsg-1~ubuntu0.16.04.1, automatic) Upgrade: libapt-inst2.0:amd64 (1.2.32ubuntu0.2, 1.2.35), update-notifier-common:amd64 (3.168.13, 3.168.14), apt:amd64 (1.2.32ubuntu0.2, 1.2.35), ubuntu-advantage-tools:amd64 (10ubuntu0.16.04.1, 27.0~16.04.1), libapt-pkg5.0:amd64 (1.2.32ubuntu0.2, 1.2.35), dpkg:amd64 (1.18.4ubuntu1.6, 1.18.4ubuntu1.7), apt-utils:amd64 (1.2.32ubuntu0.2, 1.2.35), apt-transport-https:amd64 (1.2.32ubuntu0.2, 1.2.35), libdpkg-perl:amd64 (1.18.4ubuntu1.6, 1.18.4ubuntu1.7), update-notifier:amd64 (3.168.13, 3.168.14), dpkg-dev:amd64 (1.18.4ubuntu1.6, 1.18.4ubuntu1.7) ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-10-10 (1668 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.7 apt 1.2.35 SourcePackage: ubuntu-advantage-tools Title: package ubuntu-advantage-tools 27.0~16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-advantage-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927348 Title: package ubuntu-advantage-tools 27.0~16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1927348/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914783] [NEW] package flash-kernel 3.103ubuntu1~20.10.1 failed to install/upgrade: il sottoprocesso installato pacchetto flash-kernel script post-installation ha restituito lo stato di errore 1
Public bug reported: no idea ProblemType: Package DistroRelease: Ubuntu 20.10 Package: flash-kernel 3.103ubuntu1~20.10.1 Uname: Linux 5.4.73v64 aarch64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: arm64 CasperMD5CheckResult: skip Date: Fri Feb 5 18:07:59 2021 ErrorMessage: il sottoprocesso installato pacchetto flash-kernel script post-installation ha restituito lo stato di errore 1 ImageMediaBuild: 20201022 Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.5ubuntu2 apt 2.1.10ubuntu0.2 SourcePackage: flash-kernel Title: package flash-kernel 3.103ubuntu1~20.10.1 failed to install/upgrade: il sottoprocesso installato pacchetto flash-kernel script post-installation ha restituito lo stato di errore 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: flash-kernel (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package arm64 groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914783 Title: package flash-kernel 3.103ubuntu1~20.10.1 failed to install/upgrade: il sottoprocesso installato pacchetto flash-kernel script post- installation ha restituito lo stato di errore 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1914783/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907300] Re: window resizes incorrectly across different screens
The bug no longer appears as of 5.8.0-40 ** Changed in: update-manager (Ubuntu) Status: New => 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/1907300 Title: window resizes incorrectly across different screens To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1907300/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1181666] Re: gnome-shell randomly blocks mouse clicks from working in app windows
Today I had the same issue on archlinux with kernel 5.9.14 and gnome shell 3.38.2, it happend right after taking an areal screenshot with gnome-screenshot while in fullscreen, after that when I hovered windows bar and the side dock the cursor became the classic cross you see while taking screenshots and left/right clicking didn't give any result. gnome-screenshot was called by a keyboard shortcut. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1181666 Title: gnome-shell randomly blocks mouse clicks from working in app windows To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1181666/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907300] Re: window resizes incorrectly across different screens
** Attachment added: "This is how the mismatched window appears." https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1907300/+attachment/5442948/+files/Schermata%20da%202020-12-12%2015-17-08.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907300 Title: window resizes incorrectly across different screens To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1907300/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907300] [NEW] window resizes incorrectly across different screens
Public bug reported: Hiding the details on a different screen from the one they were shown on causes the white background of the window to appear shifted w.r.t the border. This happens regardless of the screen it is done on and in all phases of the update process, including when the details disappear at the end. Moving the window on a different screen fixes the mismatch. To reproduce: 1) launch update-manager while having updates to install; 2) click on the "Details" button to show the details; 3) move the window on a different screen; 4) click again on "Details". ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: update-manager 1:20.10.1 ProcVersionSignature: Ubuntu 5.8.0-31.33-generic 5.8.17 Uname: Linux 5.8.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Dec 8 20:43:51 2020 ExecutablePath: /usr/bin/update-manager InstallationDate: Installed on 2019-05-28 (559 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) InterpreterPath: /usr/bin/python3.8 PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 SourcePackage: update-manager UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: update-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907300 Title: window resizes incorrectly across different screens To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1907300/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905843] [NEW] package virtualbox-ext-pack 6.1.14-2 failed to install/upgrade: installed virtualbox-ext-pack package post-installation script subprocess returned error exit status 1
Public bug reported: While upgrading from Focal to Groovy I got this upgrade problem ProblemType: Package DistroRelease: Ubuntu 20.10 Package: virtualbox-ext-pack 6.1.14-2 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Nov 27 08:09:46 2020 ErrorMessage: installed virtualbox-ext-pack package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2019-04-20 (586 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.20.5ubuntu2 apt 2.1.10 SourcePackage: virtualbox-ext-pack Title: package virtualbox-ext-pack 6.1.14-2 failed to install/upgrade: installed virtualbox-ext-pack package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to groovy on 2020-11-27 (0 days ago) ** Affects: virtualbox-ext-pack (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905843 Title: package virtualbox-ext-pack 6.1.14-2 failed to install/upgrade: installed virtualbox-ext-pack package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox-ext-pack/+bug/1905843/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873052] Re: Showing two cursors after login
For anyone who might be interested, since in my case this problem is caused by fractional scaling, in my Ubuntu 20.04 (and then also 20.10) installation I was able to "automatically fix" it every login by using this very small program I developed: https://github.com/mind-overflow /gnome-fs-duplicate-cursor-fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873052 Title: Showing two cursors after login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1873052/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829221] Re: second, dead, mouse pointer left on screen after login, x11 session
*** This bug is a duplicate of bug 1873052 *** https://bugs.launchpad.net/bugs/1873052 I don't think there is an official solution to this yet, however, in my Ubuntu 20.04 (and then also 20.10) installation I was able to automatically fix it every login by using this very small program I developed: https://github.com/mind-overflow/gnome-fs-duplicate-cursor- fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829221 Title: second, dead, mouse pointer left on screen after login, x11 session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1829221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901433] [NEW] i can't boot on the new kernel but i can on the old one when i change it in the grub menu ( dual boot with windows10 )
Public bug reported: i can't boot on the new kernel but i can on the old one when i change it in the grub menu ( dual boot with windows10 ), i have noticed that booting on the old one the nvidia driver doesn't work correctly but downgrading it didn't solve the problem . I'm on a lenovo ideapad 100-15IBD These are my specs with "sudo inxi -Fx" System: Host: lorenzo-Lenovo-ideapad-100-15IBD Kernel: 5.4.0-26-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 Desktop: Cinnamon 4.6.7 Distro: Linux Mint 20 Ulyana base: Ubuntu 20.04 focal Machine: Type: Laptop System: LENOVO product: 80QQ v: Lenovo ideapad 100-15IBD serial: PF0Q8PGB Mobo: LENOVO model: Nano 5B6 v: SDK0J40700 WIN serial: PF0Q8PGB UEFI: LENOVO v: E0CN63WW date: 10/21/2016 Battery: ID-1: BAT0 charge: 11.8 Wh condition: 19.9/31.7 Wh (63%) model: GC 15L4A01 status: Unknown CPU: Info: Dual Core model: Intel Core i5-4288U bits: 64 type: MT MCP arch: Haswell rev: 1 L2 cache: 3072 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 20750 Speed: 798 MHz min/max: 800/3100 MHz Core speeds (MHz): 1: 798 2: 798 3: 798 4: 798 Graphics: Device-1: Intel Haswell-ULT Integrated Graphics vendor: Lenovo driver: i915 v: kernel bus ID: 00:02.0 Device-2: NVIDIA GM108M [GeForce 920MX] vendor: Lenovo driver: nouveau v: kernel bus ID: 04:00.0 Device-3: Chicony Lenovo EasyCamera type: USB driver: uvcvideo bus ID: 2-6:3 Display: server: X.Org 1.20.8 driver: modesetting unloaded: fbdev,vesa resolution: 1366x768~60Hz OpenGL: renderer: Mesa DRI Intel Iris Graphics 5100 (HSW GT3) v: 4.5 Mesa 20.3.0-devel (git-556bb17 2020-10-10 focal-oibaf-ppa) direct render: Yes Audio: Device-1: Intel Haswell-ULT HD Audio vendor: Lenovo driver: snd_hda_intel v: kernel bus ID: 00:03.0 Device-2: Intel 8 Series HD Audio vendor: Lenovo driver: snd_hda_intel v: kernel bus ID: 00:1b.0 Sound Server: ALSA v: k5.4.0-26-generic Network: Device-1: Realtek RTL810xE PCI Express Fast Ethernet vendor: Lenovo driver: r8169 v: kernel port: 5000 bus ID: 02:00.0 IF: enp2s0 state: down mac: c8:5b:76:fe:9e:dc Device-2: Realtek RTL8723BE PCIe Wireless Network Adapter vendor: Lenovo driver: rtl8723be v: kernel port: 4000 bus ID: 03:00.0 IF: wlp3s0 state: up mac: c8:3d:d4:98:5e:cf IF-ID-1: lxcbr0 state: down mac: 00:16:3e:00:00:00 Drives: Local Storage: total: 931.51 GiB used: 151.47 GiB (16.3%) ID-1: /dev/sda vendor: Seagate model: ST1000LM035-1RK172 size: 931.51 GiB temp: 37 C Partition: ID-1: / size: 566.35 GiB used: 151.44 GiB (26.7%) fs: ext4 dev: /dev/sda5 Swap: ID-1: swap-1 type: file size: 2.00 GiB used: 0 KiB (0.0%) file: /swapfile Sensors: System Temperatures: cpu: 45.0 C mobo: N/A Fan Speeds (RPM): N/A Info: Processes: 236 Uptime: 18m Memory: 7.70 GiB used: 1.36 GiB (17.7%) Init: systemd runlevel: 5 Compilers: gcc: 9.3.0 Packages: 3335 Shell: Bash v: 5.0.17 inxi: 3.1.07 ** Affects: ubuntu Importance: Undecided Status: New ** Tags: kernel-bug -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901433 Title: i can't boot on the new kernel but i can on the old one when i change it in the grub menu ( dual boot with windows10 ) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1901433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882212] Re: Cursor blinks/flickers on screen refresh (only on built in monitor)
This seems to fix it, only a minor bug appears: I'm now unable to drag and drop icons on the desktop, once I "grab" them, they are stuck to my pointer but I can't release them. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882212 Title: Cursor blinks/flickers on screen refresh (only on built in monitor) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1882212/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882212] Re: Cursor blinks/flickers on screen refresh (only on built in monitor)
Do you need any more information? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882212 Title: Cursor blinks/flickers on screen refresh (only on built in monitor) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1882212/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882212] Re: Cursor blinks/flickers on screen refresh (only on built in monitor)
* Disabling fractional scaling in Settings. - Did not solve the issue * Using a scaling factor of 100%, briefly. - Did not solve the issue and makes the built-in monitor unusable as text size is too small * Selecting 'Ubuntu on Wayland' from the login screen. - Solves the flickering but makes text on built-in monitor too small - If I change scaling for the built-in monitor some inconsistencies are produced: - Application scaling is ok - Icons on the desktop don't change scaling All the testing has been done by logging out and back in after every change -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882212 Title: Cursor blinks/flickers on screen refresh (only on built in monitor) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1882212/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882212] Re: Cursor blinks/flickers on screen refresh (only on built in monitor)
** Summary changed: - Cursor blinks on screen refresh (only on built in monitor) + Cursor blinks/flickers on screen refresh (only on built in monitor) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882212 Title: Cursor blinks/flickers on screen refresh (only on built in monitor) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1882212/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882212] Re: Cursor blinks on screen refresh (only on built in monitor)
** Summary changed: - Arrow blinks on screen refresh (only on built in monitor) + Cursor blinks on screen refresh (only on built in monitor) ** Description changed: I have a double monitor setup, my laptop has a built-in 4k screen and my external is 1080p. - When I use the mouse on the external screen the arrow indicator has no problem but when I go on the built-in monitor the arrow indicator will blink (disappear and reappear) every time there is some kind of refresh on either screen (e.g. I type something or something is displaying text in the terminal). + When I use the mouse on the external screen the cursor has no problem but when I go on the built-in monitor the pointer will blink (disappear and reappear) every time there is some kind of refresh on either screen (e.g. I type something or something is displaying text in the terminal). My current display settings are: Display Mode: Join Displays Primary Display: either doesn't make any difference Built in display: - Orientation: Landscape - Resolution: 3840x2160 - Refresh Rate: 60,00Hz - Scale: 200% - Fractional Scaling: ON External Display: - Orientation: Landscape - Resolution: 1920x1080 - Refresh Rate: 60,00Hz - Scale: 100% - Fractional Scaling: ON Ubuntu release: 20.04 LTS Xorg version: 1:7.7+19ubuntu14 - Expected behavior: Arrow doesn't blink - Current behavior: Arrow blinks + Expected behavior: Pointer doesn't blink + Current behavior: Pointer blinks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 5 10:27:31 2020 DistUpgraded: 2020-04-24 10:45:52,182 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: - nvidia, 440.64, 5.4.0-31-generic, x86_64: installed - nvidia, 440.64, 5.4.0-33-generic, x86_64: installed + nvidia, 440.64, 5.4.0-31-generic, x86_64: installed + nvidia, 440.64, 5.4.0-33-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: - Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) -Subsystem: ASUSTeK Computer Inc. HD Graphics 530 [1043:1080] -Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 960M] [1043:1080] + Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) + Subsystem: ASUSTeK Computer Inc. HD Graphics 530 [1043:1080] + Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 960M] [1043:1080] InstallationDate: Installed on 2019-07-04 (336 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: ASUSTeK COMPUTER INC. N501VW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=acb2d85b-81be-4cf8-8e76-5abca360479b ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-24 (41 days ago) dmi.bios.date: 04/17/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N501VW.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N501VW dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN501VW.307:bd04/17/2019:svnASUSTeKCOMPUTERINC.:pnN501VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN501VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: N dmi.product.name: N501VW dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 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 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882212 Title: Cursor blinks on screen refresh (only on built in monitor) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1882212/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com
[Bug 1882212] [NEW] Cursor blinks on screen refresh (only on built in monitor)
Public bug reported: I have a double monitor setup, my laptop has a built-in 4k screen and my external is 1080p. When I use the mouse on the external screen the arrow indicator has no problem but when I go on the built-in monitor the arrow indicator will blink (disappear and reappear) every time there is some kind of refresh on either screen (e.g. I type something or something is displaying text in the terminal). My current display settings are: Display Mode: Join Displays Primary Display: either doesn't make any difference Built in display: - Orientation: Landscape - Resolution: 3840x2160 - Refresh Rate: 60,00Hz - Scale: 200% - Fractional Scaling: ON External Display: - Orientation: Landscape - Resolution: 1920x1080 - Refresh Rate: 60,00Hz - Scale: 100% - Fractional Scaling: ON Ubuntu release: 20.04 LTS Xorg version: 1:7.7+19ubuntu14 Expected behavior: Arrow doesn't blink Current behavior: Arrow blinks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 5 10:27:31 2020 DistUpgraded: 2020-04-24 10:45:52,182 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-31-generic, x86_64: installed nvidia, 440.64, 5.4.0-33-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 530 [1043:1080] Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 960M] [1043:1080] InstallationDate: Installed on 2019-07-04 (336 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: ASUSTeK COMPUTER INC. N501VW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=acb2d85b-81be-4cf8-8e76-5abca360479b ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-24 (41 days ago) dmi.bios.date: 04/17/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N501VW.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N501VW dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN501VW.307:bd04/17/2019:svnASUSTeKCOMPUTERINC.:pnN501VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN501VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: N dmi.product.name: N501VW dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 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/1882212 Title: Cursor blinks on screen refresh (only on built in monitor) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1882212/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878982] [NEW] Discover starts up with other window's contents displayed
Public bug reported: When I start Discover to install updates, the window appears to be a "copy" of another window I have open. For instance, if I'm reading Wikipedia in an open Firefox window, Discover's window will show whatever article I have open at the moment. After a few seconds, this is replaced by the spinning "loading" icon, and after this point Discover works as normal. It's not just Firefox; I've had it copy other applications, as well as my desktop background. However, opening Discover for a second time does not cause this issue. I'm not sure if the rule is that it happens the first time each login, or only when there are new updates pending. I can drag the window around as normal while it's in this state. I'm not sure what happens if I resize it. I would expect the buffer to be initialized (to, say, the spinning "loading" icon) before display. The bug is particularly noticeable because it sticks around for several seconds, but even one frame would be jarring and unexpected. I don't have any similar issues with my other applications on this machine, which has an Nvidia GPU (proprietary drivers). I don't have this particular issue on my laptop, which has Intel integrated graphics. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: plasma-discover 5.18.4.1-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Fri May 15 15:45:01 2020 InstallationDate: Installed on 2019-12-30 (136 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-kitty PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh SourcePackage: plasma-discover UpgradeStatus: Upgraded to focal on 2020-04-25 (19 days ago) ** Affects: plasma-discover (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/1878982 Title: Discover starts up with other window's contents displayed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-discover/+bug/1878982/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869879] [NEW] package libreoffice-core 1:5.1.6~rc2-0ubuntu1~xenial6 failed to install/upgrade: impossibile copiare i dati estratti per "./usr/lib/libreoffice/program/libmergedlo.so" in "/usr/lib
Public bug reported: in seguito alla installazione su laptop asus x61sl, al momento del riavvio per installazione terminata mi è uscita la dicitura "no caching mode page found" assuming drive cache" forzando il riavvio si accendeva ma non mi caricava le icone nella barra di sistema ne mi permetteva di accedere ai programmi/icone della dock. Funziona solo ctrl+alt+f1, ho provato vari codici trovati sui forum ufficiali e non. facendo upgrade di versione mi ha dato questo bug. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libreoffice-core 1:5.1.6~rc2-0ubuntu1~xenial6 ProcVersionSignature: Ubuntu 4.15.0-45.48~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Tue Mar 31 14:54:25 2020 ErrorMessage: impossibile copiare i dati estratti per "./usr/lib/libreoffice/program/libmergedlo.so" in "/usr/lib/libreoffice/program/libmergedlo.so.dpkg-new": fine del file o dello stream inattesa InstallationDate: Installed on 2020-03-31 (0 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190227) RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.32 SourcePackage: libreoffice Title: package libreoffice-core 1:5.1.6~rc2-0ubuntu1~xenial6 failed to install/upgrade: impossibile copiare i dati estratti per "./usr/lib/libreoffice/program/libmergedlo.so" in "/usr/lib/libreoffice/program/libmergedlo.so.dpkg-new": fine del file o dello stream inattesa UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869879 Title: package libreoffice-core 1:5.1.6~rc2-0ubuntu1~xenial6 failed to install/upgrade: impossibile copiare i dati estratti per "./usr/lib/libreoffice/program/libmergedlo.so" in "/usr/lib/libreoffice/program/libmergedlo.so.dpkg-new": fine del file o dello stream inattesa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1869879/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864109] [NEW] wireguard-dkms 0.0.20191206-wg1~bionic: wireguard kernel module failed to build
Public bug reported: - ProblemType: Package DistroRelease: Ubuntu 19.10 Package: wireguard-dkms 0.0.20191206-wg1~bionic ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 DKMSKernelVersion: 5.3.0-40-generic Date: Wed Feb 19 16:23:12 2020 DuplicateSignature: dkms:wireguard-dkms:0.0.20191206-wg1~bionic:/var/lib/dkms/wireguard/0.0.20191206/build/socket.c:145:20: error: ‘const struct ipv6_stub’ has no member named ‘ipv6_dst_lookup’; did you mean ‘ipv6_dst_lookup_flow’? PackageArchitecture: all PackageVersion: 0.0.20191206-wg1~bionic Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.17-1 RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: wireguard Title: wireguard-dkms 0.0.20191206-wg1~bionic: wireguard kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: wireguard (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864109 Title: wireguard-dkms 0.0.20191206-wg1~bionic: wireguard kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wireguard/+bug/1864109/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825963] Re: Abysmal memory leak on tracker-extract
I confirm the bug with DDS files (for an HOI4 mod) in 19.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825963 Title: Abysmal memory leak on tracker-extract To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1825963/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825963] Re: Abysmal memory leak on tracker-extract
I confirm the bug on 19.10 for DDS files ( from a mod for HOI4) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825963 Title: Abysmal memory leak on tracker-extract To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1825963/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854895] Re: touchpad stopped working after the update
I upadate from kernel 4.15.0-70-generic wiht same problem. Workaround was boot from old kernel on dell notebook 3458 Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ Synaptics TM3096-001 id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Button id=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Button id=8[slave keyboard (3)] ↳ Sleep Button id=9[slave keyboard (3)] ↳ Integrated_Webcam_HD: Integrate id=10 [slave keyboard (3)] ↳ Dell WMI hotkeys id=12 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=13 [slave keyboard (3)] ↳ DELL Wireless hotkeys id=14 [slave keyboard (3)] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854895 Title: touchpad stopped working after the update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1854895/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849421] [NEW] nautilus-python must depends on Python3 not Python 2.7
Public bug reported: As Python 2.7 will be deprecated in a few months... Why nautilus-python dependes on Python and not Python3? ** Affects: nautilus-python (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/1849421 Title: nautilus-python must depends on Python3 not Python 2.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus-python/+bug/1849421/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848974] Re: update-notifier fails on ALL sources if ONE source is bad
@Sebastien affect also me Ubuntu 19.04 1. The specific steps or actions you took that caused you to encounter the problem. add currently broken adoptopenjdk repository: wget -qO - https://adoptopenjdk.jfrog.io/adoptopenjdk/api/gpg/key/public | sudo apt-key add - sudo add-apt-repository --yes https://adoptopenjdk.jfrog.io/adoptopenjdk/deb/ 2. The behavior you expected. I think notify for an update also if a source is broken 3. The behavior you actually encountered (in as much detail as possible). No update found, only error of broken source ** Attachment added: "Screenshot of notification" https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1848974/+attachment/5298856/+files/Untitled.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848974 Title: update-notifier fails on ALL sources if ONE source is bad To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1848974/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840516] Re: misleading sort icon
As stated from António Fernandes (see nautilus issue #1008 linked previous message) there is an option of GTK-3 that tune this behavior, so to return to the same behavior that was in 18.04 for example a user can apply follow setting ~/.config/gtk-3.0/settings.ini [Settings] gtk-alternative-sort-arrows = true -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840516 Title: misleading sort icon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1840516/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840516] [NEW] misleading sort icon
Public bug reported: I report here because but this problem is related to amost any applicatin in Disco version 19.04 I recently installed, may something only related to a few users because I surprised not already pointed out by anyone else. Attached a screenshoot from where you should see sort icon not coherent to sorting itself. This problem affects almost any app from nautilus to rhythmbox and is very problematic at least for me. Some discussion about it in Nautilus here : https://gitlab.gnome.org/GNOME/nautilus/issues/1008 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: rhythmbox 3.4.3-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18 Uname: Linux 5.0.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Aug 17 00:54:13 2019 InstallationDate: Installed on 2019-08-10 (6 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: rhythmbox UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco ** Attachment added: "wrong sort icon example" https://bugs.launchpad.net/bugs/1840516/+attachment/5282941/+files/wrong-sort-icon.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840516 Title: misleading sort icon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1840516/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726595] Re: Running Matlab (R) from ssh session with X forwarding doesn't work anymore in 17.10
I have similar problem explained through attachment video, that happens when I focus opened window by through x11 forwarding using ssh and then I cannot raise up any of already opened window from the dock. Steps to reproduce: - open a gnome terminal so that it happears on the side dock - xhost +somehost ; ssh -X somehost - run some gui app and maximize - click on the window opened by the app so that it got focus - bug here: now click on terminal on dock and an alert message indicate that is ready but it cannot raise even with a second click Workaround: - click on the x11 forwarded app titlebar - click on terminal or other app available on the dock - the requested app window now raises ** Attachment added: "repro" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1726595/+attachment/5282644/+files/Peek%202019-08-15%2014-01.mp4 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726595 Title: Running Matlab (R) from ssh session with X forwarding doesn't work anymore in 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1726595/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811504] Re: scan with Laserjet MFP-M28 fails
Did you have to install a binary plugin (using hp-plugin) for it to work, Thomas? (In theory none is required for this model.) Did it work with Simple Scan without changing anything in particular? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811504 Title: scan with Laserjet MFP-M28 fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1811504/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827284] Re: [regression] No window spread animation in gnome-shell 3.28.3+git20190124
I'm extremely sorry. While trying to see what the different statuses mean, I accidentally changed the bug status to "fix released" and launchpad doesn't let me undo my mistake. I hope this doesn't cause any trouble. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827284 Title: [regression] No window spread animation in gnome-shell 3.28.3+git20190124 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1827284/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827284] Re: [regression] No window spread animation in gnome-shell 3.28.3+git20190124
** Changed in: gnome-shell (Ubuntu Bionic) Status: Fix Committed => 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/1827284 Title: [regression] No window spread animation in gnome-shell 3.28.3+git20190124 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1827284/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827304] Re: Linux 5.0.0-13 In Upgrade From Cosmic to Disco Broke Synaptic Touchpad
>Probably your device can't work well under i2c bus. > >please have a try: >add "psmouse.synaptics_intertouch=0" to the kernel bootargs. Yep, that fixed it! Hope all of this information can help patch it for anyone else affected! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827304 Title: Linux 5.0.0-13 In Upgrade From Cosmic to Disco Broke Synaptic Touchpad To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827304] [NEW] Linux 5.0.0-13 In Upgrade From Cosmic to Disco Broke Synaptic Touchpad
Public bug reported: In a Kubuntu Cosmic install, I had a working Synaptic touchpad. Upon upgrading to Disco, and only while on the 5.0.0-13 kernel, I lose touchpad support. It appears that the kernel still properly finds it and loads the psmouse module, but libinput does not receive any input from the device at all. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-13-generic 5.0.0-13.14 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: harley 1708 F pulseaudio CurrentDesktop: KDE Date: Wed May 1 21:15:15 2019 InstallationDate: Installed on 2019-04-10 (21 days ago) InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0a5c:216d Broadcom Corp. BCM43142A0 Bluetooth 4.0 Bus 001 Device 003: ID 1a40:0101 Terminus Technology Inc. Hub Bus 001 Device 002: ID 064e:c346 Suyin Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Notebook ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=0418c64c-d98d-4189-acc8-7f845203fc16 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2019-04-18 (13 days ago) dmi.bios.date: 05/19/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.09 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 81F1 dmi.board.vendor: HP dmi.board.version: 64.29 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.09:bd05/19/2016:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn81F1:rvr64.29:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.sku: X0S19UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug disco ** Attachment added: "/proc/bus/input/devices" https://bugs.launchpad.net/bugs/1827304/+attachment/5260639/+files/devices -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827304 Title: Linux 5.0.0-13 In Upgrade From Cosmic to Disco Broke Synaptic Touchpad To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827304] Re: Linux 5.0.0-13 In Upgrade From Cosmic to Disco Broke Synaptic Touchpad
** Attachment added: "evtest /dev/input/event7" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827304/+attachment/5260655/+files/evtest -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827304 Title: Linux 5.0.0-13 In Upgrade From Cosmic to Disco Broke Synaptic Touchpad To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827304] Re: Linux 5.0.0-13 In Upgrade From Cosmic to Disco Broke Synaptic Touchpad
** Attachment added: "/var/log/Xorg0.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827304/+attachment/5260656/+files/Xorg.0.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827304 Title: Linux 5.0.0-13 In Upgrade From Cosmic to Disco Broke Synaptic Touchpad To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826927] [NEW] at the end of the installer, it gives me this grub error
Public bug reported: Error installing grub ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: ubiquity 19.04.9 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CasperVersion: 1.405 Date: Mon Apr 29 20:53:26 2019 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed acpi=off boot=casper only-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco ubiquity-19.04.9 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826927 Title: at the end of the installer, it gives me this grub error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1826927/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1812935] Re: oslo cache mempool issues with python3
I can confirm it works. The rocky-proposed package python-oslo.cache-1.30.1-0ubuntu1.1 fixes bug #1822541 too. I manually upgraded the n-c-c units on a Rocky cloud (applying the proper bindings for n-c-c & memcached according with the comment #14 of bug #1823740) to get the new python-oslo packaged installed and now n-c-c fully works. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1812935 Title: oslo cache mempool issues with python3 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1812935/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824033] [NEW] Libreoffice Core Application Missing Application Icon In Plasma Task Manager
Public bug reported: The main core application for Libreoffice is missing its icon in the Task Manager when opened in Plasma. May affect other desktop environments. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: libreoffice-core 1:6.2.2-0ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu26 Architecture: amd64 CurrentDesktop: KDE Date: Tue Apr 9 18:31:36 2019 ExecutablePath: /usr/lib/libreoffice/program/soffice.bin InstallationDate: Installed on 2019-04-08 (1 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco ** Attachment added: "Screenshot of its appearance" https://bugs.launchpad.net/bugs/1824033/+attachment/5254539/+files/Screenshot_20190409_183628.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824033 Title: Libreoffice Core Application Missing Application Icon In Plasma Task Manager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1824033/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824034] [NEW] Spectacle Closes Unexpectedly When Screenshot Notifications Close
Public bug reported: If a screenshot notification closes while the spectacle window is open, the spectacle window will close unexpectedly. Steps to reproduce: 1. Take a screenshot via a hotkey (so the spectacle notification appears) 2. Open spectacle so the main window appears 3. Close the notification (or wait for it to automatically close) and watch as the spectacle window, which is unrelated to the screenshot notification, close because of the screenshot notification Expected behavior: Spectacle window unaffected by other screenshot notifications closing ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: kde-spectacle 18.12.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu26 Architecture: amd64 CurrentDesktop: KDE Date: Tue Apr 9 18:39:33 2019 ExecutablePath: /usr/bin/spectacle InstallationDate: Installed on 2019-04-08 (1 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: kde-spectacle UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: kde-spectacle (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824034 Title: Spectacle Closes Unexpectedly When Screenshot Notifications Close To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kde-spectacle/+bug/1824034/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824031] [NEW] Plasma Manager Rapidly Animated Loading Overlay
Public bug reported: In the both the standard and icons-only task manager in plasma, the loading overlay (that appears after launching an application but before the window has loaded) is rapidly animated much faster than what is intended. Note: this bug was found in a virtualbox VM and this may possibly contribute to it, but I have no reason to believe that a VM would effect this. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: plasma-workspace 4:5.15.4-0ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu26 Architecture: amd64 CurrentDesktop: KDE Date: Tue Apr 9 18:21:08 2019 ExecutablePath: /usr/bin/plasmashell InstallationDate: Installed on 2019-04-08 (1 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: plasma-workspace UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: plasma-workspace (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824031 Title: Plasma Manager Rapidly Animated Loading Overlay To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-workspace/+bug/1824031/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823793] Re: [regression] Font scaling not working on gnome startup
Version 3.32.0-1ubuntu2 has also fixed the issue for me. I believe it is triaged. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823793 Title: [regression] Font scaling not working on gnome startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1823793/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823793] Re: Font scaling not working on gnome startup
I did some testing on this too, and after you log back in and everything is visually set back to 1 you have to manually set it back to 1 then back to 1.25 to get the font scaling to work. Setting it to 1.25 immediately results in no change and it staying at 1. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823793 Title: Font scaling not working on gnome startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1823793/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823617] Re: Setting Custom Resolution Doesn't Work (Virtualmachine)
** Summary changed: - Virtualmachine Setting Resolution Doesn't Work + Setting Custom Resolution Doesn't Work (Virtualmachine) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823617 Title: Setting Custom Resolution Doesn't Work (Virtualmachine) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kde-cli-tools/+bug/1823617/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823617] [NEW] Virtualmachine Setting Resolution Doesn't Work
Public bug reported: Setting the screen resolution explicitly from anything instead of the default 800x600 resolution while Disco Kubuntu is booted from a virtual- machine (Virtualbox) is met with the resolution switching quickly to what's expected followed by it immediately switching back to 800x600. Testing this in GNOME afterward is not met with this bug. Guest Additions (proprietary) testing (This utilizes the proprietary guest addition add-ons from Virtualbox to further test the limits of the bug, but since the guest additions are proprietary additions to the operating system, I am separating it.) With Guest Additions installed, Plasma is able to stay with the auto-scaled resolution correctly, but setting any specific resolution is met with it switching back to the auto-scaled resolution much like how it would switch back to 800x600 earlier. GNOME is still able to switch to other resolutions without any problem with Guest Additions installed. I am unable to test if this bug affects actual real machines and hardware or if it is a virtual monitor specific bug. I was using the KDE Displays settings GUI (kcmshell5 kcm_screen) while encountering this bug. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: kde-cli-tools 4:5.15.4-0ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu25 Architecture: amd64 CurrentDesktop: KDE Date: Mon Apr 8 01:58:23 2019 ExecutablePath: /usr/bin/kcmshell5 InstallationDate: Installed on 2019-04-08 (0 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: kde-cli-tools UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: kde-cli-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823617 Title: Virtualmachine Setting Resolution Doesn't Work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kde-cli-tools/+bug/1823617/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1812130] [NEW] package friendly-recovery 0.2.39 failed to install/upgrade: installed friendly-recovery package post-installation script subprocess returned error exit status 127
Public bug reported: I don't know what the problem is but upgrading from ubuntu 18.04 to 18.10 in a machine with dual boot with windows it gave me this problem ProblemType: Package DistroRelease: Ubuntu 18.10 Package: friendly-recovery 0.2.39 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 Date: Thu Jan 17 00:39:50 2019 ErrorMessage: installed friendly-recovery package post-installation script subprocess returned error exit status 127 InstallationDate: Installed on 2019-01-11 (5 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.10 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3 RelatedPackageVersions: dpkg 1.19.0.5ubuntu5 apt 1.7.0 SourcePackage: friendly-recovery Title: package friendly-recovery 0.2.39 failed to install/upgrade: installed friendly-recovery package post-installation script subprocess returned error exit status 127 UpgradeStatus: Upgraded to cosmic on 2019-01-16 (0 days ago) ** Affects: friendly-recovery (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package cosmic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1812130 Title: package friendly-recovery 0.2.39 failed to install/upgrade: installed friendly-recovery package post-installation script subprocess returned error exit status 127 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/1812130/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1281580] Re: glib-compile-schemas doesn't compile relocatable schemas
It is possible that this bug is open from 2014 and no one fixed the bug? I've been last couple of days trying to create a gschema.override file with relocatable schemas and now I understands that there is a bug unfixed. I'm on Debian 9.5 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1281580 Title: glib-compile-schemas doesn't compile relocatable schemas To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1281580/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1288003] Re: wifi no worky unless laptop lid is closed then again opened
issue solve using 4.18.0-041800rc8 I had same trouble with an ASUS P2530UA-XO0868D with Ubuntu 18.04 and kernel 4.15.0-30 When boot notebook within lid closed Wifi not work, I needed to open the lid, but now with latest kernel mainstream it works. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1288003 Title: wifi no worky unless laptop lid is closed then again opened To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1288003/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1781261] [NEW] terminal doesn't launches after language change
Public bug reported: after uninstalling a few languages and applying the changes system-wide, but before confirming the default language and re-logging in terminal won't launch ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-terminal 3.28.2-1ubuntu1~18.04.1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jul 11 19:15:51 2018 InstallationDate: Installed on 2018-07-05 (6 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "Screenshot from 2018-07-11 19-23-39.png" https://bugs.launchpad.net/bugs/1781261/+attachment/5162507/+files/Screenshot%20from%202018-07-11%2019-23-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/1781261 Title: terminal doesn't launches after language change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1781261/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1088178] Re: Application switchers show incorrect or no icons in gnome classic
Hi. I also confirm the problem. Using 14.04 and default Unity. My problem is the exact same as the one in the picture attached by prokher. Best. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1088178 Title: Application switchers show incorrect or no icons in gnome classic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1088178/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1257956] Re: Headphones stopped working after use of Audacity. They are detected, but no sound is produced.
Editing source in audacity to "pulse: Internal Mic 0" works on Ubuntu 18.04 and official audacity packager from their ppa version: 2.2.2-1build1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1257956 Title: Headphones stopped working after use of Audacity. They are detected, but no sound is produced. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1257956/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766648] [NEW] baloo_file crashes after some time in Ubuntu Bionic
Public bug reported: After some time of use, baloo_file crashes; after this happens, baloo has to be started again manually, but modifying any file leads to the same crash. The only way of making it work again is to "disable" it and then "enable" it, so that the index is completely recreated... thus the problem could be the index gets easily corrupted? Application: baloo_file (5.44.0) Qt Version: 5.9.5 Frameworks Version: 5.44.0 Operating System: Linux 4.15.0-19-generic x86_64 Distribution: Ubuntu Bionic Beaver (development branch) -- Backtrace: Application: Baloo File Indexing Daemon (baloo_file), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f896c49f200 (LWP 4997))] Thread 2 (Thread 0x7f8961b02700 (LWP 5007)): #0 0x7f8969e51bf9 in __GI___poll (fds=0x7f895c003ce0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f89665b5439 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f89665b554c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f896ab3d90b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f896aae29ea in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f896a90122a in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f896bd51d45 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7f896a90616d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f8968e846db in start_thread (arg=0x7f8961b02700) at pthread_create.c:463 #9 0x7f8969e5e88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7f896c49f200 (LWP 4997)): [KCrash Handler] #6 __memmove_avx_unaligned_erms () at ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:427 #7 0x7f896b260973 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5 #8 0x7f896b2523e4 in Baloo::PostingDB::get(QByteArray const&) () from /usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5 #9 0x7f896b25e060 in Baloo::WriteTransaction::commit() () from /usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5 #10 0x7f896b257942 in Baloo::Transaction::commit() () from /usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5 #11 0x557479809958 in ?? () #12 0x7f896ab136cf in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x5574798120e5 in ?? () #14 0x55747980797e in ?? () #15 0x7f896ab136cf in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x7f896ab20027 in QTimer::timeout(QTimer::QPrivateSignal) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x7f896ab20388 in QTimer::timerEvent(QTimerEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x7f896ab140db in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x7f896aae4991 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x7f896ab3cd8e in QTimerInfoList::activateTimers() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #21 0x7f896ab3d551 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x7f89665b5287 in g_main_context_dispatch () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #23 0x7f89665b54c0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #24 0x7f89665b554c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #25 0x7f896ab3d8ef in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #26 0x7f896aae29ea in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #27 0x7f896aaeba84 in QCoreApplication::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #28 0x5574797f380c in ?? () #29 0x7f8969d5eb97 in __libc_start_main (main=0x5574797f3560, argc=1, argv=0x7ffdf65abf18, init=, fini=, rtld_fini=, stack_end=0x7ffdf65abf08) at ../csu/libc-start.c:310 #30 0x5574797f3a7a in _start () ** Affects: baloo (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/1766648 Title: baloo_file crashes after some time in Ubuntu Bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/baloo/+bug/1766648/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1752445] Re: baloo_file crashed with SIGSEGV in __memmove_avx_unaligned_erms()
*** This bug is a duplicate of bug 1749569 *** https://bugs.launchpad.net/bugs/1749569 but the original bug #1749569 is not accessible, is it? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1752445 Title: baloo_file crashed with SIGSEGV in __memmove_avx_unaligned_erms() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/baloo-kf5/+bug/1752445/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1579652] Re: snap ignores the proxy environment variables
It looks like http_proxy isn't picked by snap. Because I am using an authenticating proxy I'm not sure I should put that information in a system-wide /etc/environment Why can't snap just use standard environment variables http_proxy? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1579652 Title: snap ignores the proxy environment variables To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1579652/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1678674] Re: Possibly considering the touchscreen as an "external mouse"
** Changed in: touchpad-indicator Assignee: (unassigned) => Lorenzo Carbonell (lorenzo-carbonell) ** Changed in: touchpad-indicator Status: New => 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/1678674 Title: Possibly considering the touchscreen as an "external mouse" To manage notifications about this bug go to: https://bugs.launchpad.net/touchpad-indicator/+bug/1678674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1336521] Re: Application Startup Notify fully ignored
Chris J Arges, 4 years have passed but thank you for your support. :-) The startup notification now works but has some big flaws. Since this is a patch to openbox I will do the tests in a stable and standard-compliant environment to see if the bug persists or not. Environment: Debian GNU/Linux 9 (stretch) with XFCE 4 + Openbox 3.6.1-4 + notification-daemon installed Hardware: Core i5, 8Gb RAM CHANGELOG: openbox (3.6.1-3) unstable; urgency=medium * debian/control: + Bump Standards-Version to 3.9.8. + Use secured links for VCS. + Add libxcursor-dev to B-D. (Closes: #838326, LP: #1336521) NOTE: "LP: #1336521" is *this* bug in notifications. Tests: [Test Case 1] 0. Started cpulimit to limit the execution to 3% of the total CPU power. 1. Started Cheese 3.22.1 with startup notifications enabled (manually enabled from desktop file) from a desktop file. 2. No spinning cursor at all. Failed. [Test Case 2] 0. Started cpulimit to limit the execution to 10% of the total CPU power. 1. Started Cheese 3.22.1 with startup notifications enabled (manually enabled from desktop file) from a desktop file. 2. No spinning cursor at all. Failed. [Test Case 3] 1. Started IDLE 3.5.3 with startup notifications enabled (default) from a desktop file. 2. The spinning cursor appears only on the window and lasts for many seconds. The application has been started and the user can already work... but the cursor keeps spinning. Failed? [...many other tests with similar results, sometimes it works, other times does not] I do not know where the problem is (changelog says the issue was closed...) but I cannot say that the startup notification is correctly supported. Still, I am grateful for your efforts. Regards, Lorenzo -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1336521 Title: Application Startup Notify fully ignored To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openbox/+bug/1336521/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1744472] Re: Removing active keyboard layout crashes session
Added faulty package ** Package changed: ubuntu => gnome-settings-daemon (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1744472 Title: Removing active keyboard layout crashes session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1744472/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1744472] [NEW] Removing active keyboard layout crashes session
Public bug reported: TL;DR If you have multiple keyboard layouts and go to Settings->Region and language and remove the active one, session crashes and you are prompted to enter your password again. How to reproduce : Very easy, add a keyboard layout (Settings->Region and language) by clicking the [+] button, pick your favorite and make it the active one (or by going to the top bar and clicking on it or by pressing Meta+Space), now make sure you did this correctly by typing some text with the new layout. Once you are ready to crash your session get back to the settings, click on your active keyboard layout and click the [-] button to remove the layout, your computer will freeze for a few seconds (at least mine did) then the screen goes black and puts you on the session login page. Instead it should simply switch you on the next available one or ask you to pick another one before removing it. I have Ubuntu 17.10 on a Thinkpad, everything is up-to-date. The bug itself isn't very important but could be frustrating if a user has unsaved work. Thanks to all of you for your work, i don't miss Windows ** 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/1744472 Title: Removing active keyboard layout crashes session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1744472/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1388559] Re: failed command: WRITE FPDMA QUEUED
I got same problem using latest 4.15rc-3
ec 13 20:57:59 bigone kernel: [ 23.575115] ata10.00: status: { DRDY }
Dec 13 20:57:59 bigone kernel: [ 23.577829] ata10.00: failed command: WRITE
FPDMA QUEUED
Dec 13 20:57:59 bigone kernel: [ 23.580536] ata10.00: cmd
61/08:f0:00:08:00/00:00:02:00:00/40 tag 30 ncq dma 4096 out
Dec 13 20:57:59 bigone kernel: [ 23.580536] res
40/00:5c:e8:29:00/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
Dec 13 20:57:59 bigone kernel: [ 23.585924] ata10.00: status: { DRDY }
Dec 13 20:57:59 bigone kernel: [ 23.588651] ata10: hard resetting link
I figured out that the issue appers only when SATA disk connected to the COM4
port of the ASM1062 board while if your try to connect to the other internal
connector ( COM3 ) it doesn't report any issue at all.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1388559
Title:
failed command: WRITE FPDMA QUEUED
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1388559/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 769649] Re: awesome book
I wanted to share with you my impressions about a book I've just finished reading , it's awesome , you can find my review here http://www.andhramangoes.com/qbgx.php?UE83Njk2NDlAYnVncy5sYXVuY2hwYWQubmV0 - Bienvenue sur l'url du site web . si vous continuez à voguer et éprouvée ce site Web , vous acceptez de respecter et de s'avérer être lié par les termes et conditions de prise en main prochains , qui , grace à notre charte de confidentialité , régissent la du sexe des États-Unis avec vous à propos d' ce site Web . dans le cas ou n'êtes pas charte avec une partie de ces termes et circonstances , s.v.p. ne pas utiliser l'url du site web Web . -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/769649 Title: package smbclient 2:3.4.7~dfsg-1ubuntu3.6 failed to install/upgrade: ile tar rovinato - l'archivio del pacchetto è danneggiato To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/769649/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 769649] ✔Re: yahoo amazing people and place
Hey, I just wanted to inform you of a beautiful place I've stopped at recently, I found a whole lot of amazing people there. please learning much more about it here http://www.tctp.ca/ridge.php?UE83Njk2NDlAYnVncy5sYXVuY2hwYWQubmV0 VLTER LNG From: Bug 769649 [mailto:769...@bugs.launchpad.net] Sent: Saturday, November 11, 2017 1:47 AM To: gianluca...@libero.it Subject: Cooper...Praise Be Well the battery is okay because usually the shop will have one. The Jera run/judgement card can be found on necro or depths by blowing up skulls, the only real difficulty is getting the blank card from the shop or item room. I mean its not very easy to do but it is less luck based than the sharp plug method or even just hoping for book of revelations (in my experience that is). Sent from Mail for Windows 10 ** Attachment added: "3293FD4574A2924F.jpg" https://bugs.launchpad.net/bugs/769649/+attachment/5007234/+files/3293FD4574A2924F.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/769649 Title: package smbclient 2:3.4.7~dfsg-1ubuntu3.6 failed to install/upgrade: ile tar rovinato - l'archivio del pacchetto è danneggiato To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/769649/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1731527] [NEW] Elantech touchpad never work
Public bug reported: Since I installed Ubuntu 17.10, the touchpad has never worked. I read a lot in forums, but no one found a solution. Please, solve my problem ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-16-generic 4.13.0-16.19 [modified: boot/vmlinuz-4.13.0-16-generic] ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lorenzo1135 F pulseaudio /dev/snd/controlC0: lorenzo1135 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Nov 10 19:11:04 2017 InstallationDate: Installed on 2017-11-10 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 80XV ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed root=UUID=02baf904-cbdf-4796-a6f8-f8290963b313 ro i8042.kbdreset=1 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: 5PCN17WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 320-15AST dmi.modalias: dmi:bvnLENOVO:bvr5PCN17WW:bd07/13/2017:svnLENOVO:pn80XV:pvrLenovoideapad320-15AST:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad320-15AST: dmi.product.family: ideapad 320-15AST dmi.product.name: 80XV dmi.product.version: Lenovo ideapad 320-15AST dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug artful 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/1731527 Title: Elantech touchpad never work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1731527/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1721880] Re: can't disable wi-fi and system hangs on shutdown
You're welcome. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1721880 Title: can't disable wi-fi and system hangs on shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1721880/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1721880] Re: can't disable wi-fi and system hangs on shutdown
It's not in the official repositories yet, but I've manually installed it from here: http://kernel.ubuntu.com/~kernel-ppa/mainline/ I haven't experienced any bug so far. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1721880 Title: can't disable wi-fi and system hangs on shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1721880/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1721880] Re: can't disable wi-fi and system hangs on shutdown
I can confirm that after upgrading the kernel to 4.13.6 the problem is solved -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1721880 Title: can't disable wi-fi and system hangs on shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1721880/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1721880] Re: can't disable wi-fi and system hangs on shutdown
So we just have to wait for the kernel update, I hope it will arrive soon -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1721880 Title: can't disable wi-fi and system hangs on shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1721880/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1721880] Re: can't disable wi-fi and system hangs on shutdown
Hi again, I've got an interesting piece of news: I've recently discovered that the problem only appears when I'm connected to the optical fiber network in the flat where I live during the week; when I use ubuntu with the wi-fi at my home (much slower, at 7 Mbps) everything is working just fine. I don't know if there is a problem with the management of the fiber network in Ubuntu or if the issue is caused by a wrong configuration of the router. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1721880 Title: can't disable wi-fi and system hangs on shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1721880/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1721880] [NEW] can't disable wi-fi and system hangs on shutdown
Public bug reported: If I try to turn off wi-fi the system freezes for few seconds and after that internet is not working and I can't open settings anymore, even if the wi-fi tray icon still shows a connection. When I shutdown the system it says that "A stop job for network-manager and wpa supplicant is running" and I have to wait for 10-11 minutes. Suspension doesn't work neither. Everything was working just fine on 17.10 daily builds. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: network-manager 1.8.4-1ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 6 23:18:01 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-09-22 (14 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170917) IpRoute: default via 192.168.1.254 dev wlp3s0 proto static metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.105 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp3s0 wifi connected/org/freedesktop/NetworkManager/Devices/3 Alice_BO2f15ab74-48df-437b-b0a1-83bf31708fea /org/freedesktop/NetworkManager/ActiveConnection/1 enp2s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.8.4connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful 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/1721880 Title: can't disable wi-fi and system hangs on shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1721880/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1707361] [NEW] package libparams-validate-perl 1.22-1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
*** This bug is a duplicate of bug 1707359 *** https://bugs.launchpad.net/bugs/1707359 Public bug reported: non si aggiornano i pacchetti ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libparams-validate-perl 1.22-1 ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70 Uname: Linux 4.4.0-83-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Sat Jul 29 10:08:08 2017 DuplicateSignature: package:libparams-validate-perl:1.22-1 Processing triggers for fontconfig (2.11.94-0ubuntu1.1) ... dpkg: error processing package libparams-validate-perl (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-02-17 (161 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: libparams-validate-perl Title: package libparams-validate-perl 1.22-1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libparams-validate-perl (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1707361 Title: package libparams-validate-perl 1.22-1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libparams-validate-perl/+bug/1707361/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1707359] [NEW] package libparams-validate-perl 1.22-1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
Public bug reported: non si aggiornano i paccetti ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libparams-validate-perl 1.22-1 ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70 Uname: Linux 4.4.0-83-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Sat Jul 29 10:08:08 2017 DuplicateSignature: package:libparams-validate-perl:1.22-1 Processing triggers for fontconfig (2.11.94-0ubuntu1.1) ... dpkg: error processing package libparams-validate-perl (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-02-17 (161 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: libparams-validate-perl Title: package libparams-validate-perl 1.22-1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libparams-validate-perl (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1707359 Title: package libparams-validate-perl 1.22-1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libparams-validate-perl/+bug/1707359/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1705092] [NEW] hard disk danneggiato
Public bug reported: al momento di installare ubuntu 17.04 l'installazione si ferma riportando un errore riconducibile all'hard disk danneggiato ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: ubiquity 17.04.9 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic i686 ApportVersion: 2.20.4-0ubuntu4 Architecture: i386 CasperVersion: 1.380 Date: Tue Jul 18 20:14:11 2017 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity LiveMediaBuild: Ubuntu 17.04 "Zesty Zapus" - Release i386 (20170412) ProcEnviron: LANGUAGE=it_IT.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 ubiquity-17.04.9 ubuntu zesty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1705092 Title: hard disk danneggiato To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1705092/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1694831] [NEW] package amavisd-new 1:2.10.1-4ubuntu1 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1
Public bug reported: m ProblemType: Package DistroRelease: Ubuntu 17.04 Package: amavisd-new 1:2.10.1-4ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 Date: Wed May 31 23:18:54 2017 ErrorMessage: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1 InstallationDate: Installed on 2016-11-22 (190 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: amavisd-new Title: package amavisd-new 1:2.10.1-4ubuntu1 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1 UpgradeStatus: Upgraded to zesty on 2017-05-30 (1 days ago) ** Affects: amavisd-new (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package third-party-packages zesty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1694831 Title: package amavisd-new 1:2.10.1-4ubuntu1 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amavisd-new/+bug/1694831/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1691507] [NEW] internet connection randomly drops while WiFi is still connected
Public bug reported: I recently installed ubuntu on my new laptop. I'm having the usual struggles getting all the things working, and the latest one is the WiFi. For some reason, my internet connection drops shortly after connecting to the WiFi (but not always! sometimes it lasts for a longer time); what is weird is that my laptop is actually still connected to the WiFi, I just lose the connection to the internet. I'm sure it's not a problem of my network, because with the ethernet or other PCs it's all good. I asked this question on AskUbuntu, and as suggested I tried disabling "FW control power save" by entering "sudo tee /etc/modprobe.d/rtl8821ae.conf <<< "options rtl8821ae fwlps=0"" in a terminal. Since this didn't solve the problem, I was suggested to file a bug here. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-21-generic 4.10.0-21.23 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: brisvag1690 F pulseaudio CurrentDesktop: i3 Date: Wed May 17 17:48:26 2017 HibernationDevice: RESUME=UUID=175c3abb-fe1f-4aa0-b025-5beccc2e3fc3 InstallationDate: Installed on 2017-05-15 (2 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID b49a:04f2 Bus 001 Device 005: ID 145f:01ac Trust Bus 001 Device 002: ID 04f2:b547 Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X550VX ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-21-generic.efi.signed root=UUID=199965b7-20ca-4c45-b79e-d287852fedc9 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-21-generic N/A linux-backports-modules-4.10.0-21-generic N/A linux-firmware 1.164.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/22/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550VX.206 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550VX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX550VX.206:bd04/22/2016:svnASUSTeKCOMPUTERINC.:pnX550VX:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550VX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X550VX dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug network wifi zesty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1691507 Title: internet connection randomly drops while WiFi is still connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1691507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 769649] Re: Fw: something useful
Dear! I've got some information that may be really useful for you, please read it here http://drawbacks.mandyshomes.com Warm regards, VLTER LNG From: Bug 769649 [mailto:769...@bugs.launchpad.net] Sent: Friday, May 12, 2017 12:34 PM To: gianluca...@libero.it Subject: yeezy white t I think Supers should be replaced wit moves that require you to have a large amount of Stamina available. Also, while character creation would be good. It would be tough to nail some of the more interesting moves of some of the boss characters, like Ornstein's dashes, or Smoughs butt smash. I think there would still need to be premade characters. Sent from Mail for Windows 10 ** Attachment added: "D88E225A97616F709A879C404A66.jpg" https://bugs.launchpad.net/bugs/769649/+attachment/4875698/+files/D88E225A97616F709A879C404A66.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/769649 Title: package smbclient 2:3.4.7~dfsg-1ubuntu3.6 failed to install/upgrade: ile tar rovinato - l'archivio del pacchetto è danneggiato To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/769649/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1680699] Re: package zfsutils-linux 0.6.5.6-0ubuntu16 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Everything stored by zfs. It's the mount point. So, I can't free it up, I can unmount but is this the correct procedure to upgrade? I definitely don't want to lose my data. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1680699 Title: package zfsutils-linux 0.6.5.6-0ubuntu16 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1680699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1680699] Re: package zfsutils-linux 0.6.5.6-0ubuntu16 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
So, how to upgrade? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1680699 Title: package zfsutils-linux 0.6.5.6-0ubuntu16 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1680699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1680699] [NEW] package zfsutils-linux 0.6.5.6-0ubuntu16 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: Bug happen when trying to update the system. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: zfsutils-linux 0.6.5.6-0ubuntu16 ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49 Uname: Linux 4.4.0-72-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Fri Apr 7 07:08:52 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: zfs-linux Title: package zfsutils-linux 0.6.5.6-0ubuntu16 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: zfs-linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1680699 Title: package zfsutils-linux 0.6.5.6-0ubuntu16 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1680699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1675760] Re: rootfs issues - 2.8 LXD release
Running the containers 'init' operation in the concurrent way and looking with a 'top', you can see the related 'unsquashfs' operations running: for X in `seq 1 4`; do lxc init ubuntu: test$X & done top Waiting until the unsquashfs terminates and then starting the containers, all is good and the operation runs fine: for X in `seq 1 4`; do lxc start test$X & done The 'init' process takes some time to explode the container image on the fs. Looks like there are not any bugs but all this behaviour is due to the overall speed (disk+fs) to unsquash the containers images. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1675760 Title: rootfs issues - 2.8 LXD release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1675760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1675760] Re: rootfs issues - 2.8 LXD release
Yes, I unmounted it. getfacl: Removing leading '/' from absolute path names # file: var/lib/lxd/storage-pools/default/containers/test1 # owner: 10 # group: 10 user::rwx user:10:r-x group::r-x mask::r-x other::r-x -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1675760 Title: rootfs issues - 2.8 LXD release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1675760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1675760] Re: rootfs issues - 2.8 LXD release
VM upgraded to: Linux ubuntu 4.4.0-66-generic #87 Same behaviour. Here attached the output of the 'ls' commands. ** Attachment added: "lxd.listing" https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1675760/+attachment/4844752/+files/lxd.listing -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1675760 Title: rootfs issues - 2.8 LXD release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1675760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1675760] Re: rootfs issues - 2.8 LXD release
Here attached there is the log of a single container (test1), as requested by Christian. lxc info --show-log test1 ** Attachment added: "'test1' container log" https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1675760/+attachment/4844639/+files/test1.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1675760 Title: rootfs issues - 2.8 LXD release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1675760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1675760] Re: rootfs issues - 2.8 LXD release
cat /proc/self/mounts http://pastebin.ubuntu.com/24241515/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1675760 Title: rootfs issues - 2.8 LXD release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1675760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1675760] Re: rootfs issues - 2.8 LXD release
'lxc info' output: http://pastebin.ubuntu.com/24241376/ 'lxc config show' output: http://pastebin.ubuntu.com/24241379/ I ran: for X in `seq 1 4`; do lxc init ubuntu: test$X & done and then, after a while: for X in `seq 1 4`; do lxc start test$X & done This is what I got in the /var/log/lxd/lxd.log file: http://pastebin.ubuntu.com/24241385/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1675760 Title: rootfs issues - 2.8 LXD release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1675760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1675760] Re: rootfs issues - 2.8 LXD release
A freshly created one (KVM VM). LXD 2.12 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1675760 Title: rootfs issues - 2.8 LXD release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1675760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1675760] Re: rootfs issues - 2.8 LXD release
We ran new tests: some issue shows up even using LXD 2.12 If I run: for X in `seq 1 4`; do lxc init ubuntu: test$X & done LXD creates the containers but it can't start them. This is the output of 'lxc info --show-log test1': https://pastebin.canonical.com/183666/ If I run: for X in `seq 1 4`; do lxc init ubuntu: test$X ; done there are no issues and I can start the containers in the usual way. Looks like LXD isn't able to handle some sort of concurrency during the containers creation. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1675760 Title: rootfs issues - 2.8 LXD release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1675760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1675760] [NEW] rootfs issues - 2.8 LXD release
Public bug reported: System: Distributor ID: Ubuntu Description:Ubuntu 16.04.2 LTS Release:16.04 Codename: xenial Kernel release: 4.8.0-36 LXD release 2.8 I got a rootfs error starting few LXD containers: https://pastebin.canonical.com/183648/ This is the 'lxc list' output: https://pastebin.canonical.com/183650/ That container, named 'idm' uses an 'ovs' profile: https://pastebin.canonical.com/183649/ Here attached there is the /var/log/lxd/lxd.log file ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lxd 2.8-0ubuntu1~ubuntu16.04.1 ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11 Uname: Linux 4.8.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Fri Mar 24 12:22:59 2017 InstallationDate: Installed on 2017-03-23 (0 days ago) InstallationMedia: Ubuntu-Server 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.8) SourcePackage: lxd UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lxd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Attachment added: "LXD log file" https://bugs.launchpad.net/bugs/1675760/+attachment/4844335/+files/lxd.log.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1675760 Title: rootfs issues - 2.8 LXD release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1675760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1596381] Re: [X555UA, Realtek ALC256, Mic, Internal] No sound at all
Comment #8 worked for me too. Thank you! I'm on an Asus E402S with internal soundcard model Realtek ALC256. I'm running elementaryOS Loki. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1596381 Title: [X555UA, Realtek ALC256, Mic, Internal] No sound at all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1596381/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1522675] Re: Can't drop privileges for downloading : _apt user not allowed
** Also affects: msttcorefonts (Ubuntu) Importance: Undecided Status: New ** Changed in: msttcorefonts (Ubuntu) Status: New => Invalid ** No longer affects: msttcorefonts (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1522675 Title: Can't drop privileges for downloading : _apt user not allowed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1522675/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1578951] Re: Libreoffice is crashing causing the session to be booted back to the login screen
It worked only for some time, now (after activating OpenGl renderer) X doesn't crash but Libreoffice exit some seconds after showing CSV import window. On console I receive: intel_do_flush_locked failed: Bad address ** Attachment added: "window showed (with some glitches that occurs with OpenGl renderer)" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1578951/+attachment/4767560/+files/CSV%20import.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1578951 Title: Libreoffice is crashing causing the session to be booted back to the login screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1578951/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1578951] Re: Libreoffice is crashing causing the session to be booted back to the login screen
I could always replicate the crash opening a CSV file. Activating OpenGl renderer is a workaround. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1578951 Title: Libreoffice is crashing causing the session to be booted back to the login screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1578951/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1554613] Re: Screen flickers on XPS 13 9350/9550 (Intel Skylake/Broadwell GPU)
At least for my DELL 3800, current kernel in Ubuntu Xenial, 4.4.0-38.57, fixes the flickering -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1554613 Title: Screen flickers on XPS 13 9350/9550 (Intel Skylake/Broadwell GPU) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1554613/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1622240] [NEW] cannot switch to normal window size from fullscreen
Public bug reported: When Guake is minimized while it is in fullscreen mode and it is shown again (pushing F12), the size of the window cannot be switched to normal mode, it gets stuck at fullscreen. To reproduce the error: -launch Guake -maximize it pushing F11 -hide it pushing F12 -show it pushing F12 -try to restore window size pushing F11. It does not restore the size corretly. OS: Kubuntu 16.04 ** Affects: guake (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/1622240 Title: cannot switch to normal window size from fullscreen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/guake/+bug/1622240/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1621860] [NEW] Apps re-arranged on 2 screens config. after unlocking
Public bug reported: Hi, I have Ubuntu 16.04 installed on a Dell Latitude 3350. I have also an external monitor, HDMI connected. When I lock my screen (ctrl+alt+l) and unlock it after a while (without any system suspension happened) my program windows are all placed on one screen (the external one, because, I think, it is the closest to the top-left corner). this misplacing happens when the HDMI external monitor does not go into suspension mode (some seconds after the screen is locked): I think ubuntu does not longer see two monitors and then aggregate all windows in one screen; when I unlock, ubuntu place all of them in the external screen, even if it was the one suspended, because it becomes the main (top-right) one. Anyone suffer the same unwanted behaviour or can suggest a solution? How can I force the external monitor to not go suspended, ad/or ubuntu to hold it alive? thank you, lorenzo ** 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/1621860 Title: Apps re-arranged on 2 screens config. after unlocking To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1621860/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1619901] [NEW] links to local files are always processed as relative paths
Public bug reported: When I create a pdf with a link to an absolute path (e.g. /home/me/link.pdf) and open it in evince it tries to read it as relative to the path of the opened pdf, e.g. if I open /home/me/doc.pdf and click on the preceding link evince tries to open /home/me/home/me/link.pdf. It should open /home/me/link.pdf, otherwise the user is unable to link to files outside the local directory Ubuntu 16.04.1 Evince 3.18.2-1ubuntu4 ** Affects: evince (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/1619901 Title: links to local files are always processed as relative paths To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1619901/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
