[Bug 2064028] Re: after upgade ubuntu from 23.10 to 24.04 no if-up.d script are executed after connecting to openconnect vpn
** Also affects: openconnect 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/2064028 Title: after upgade ubuntu from 23.10 to 24.04 no if-up.d script are executed after connecting to openconnect vpn To manage notifications about this bug go to: https://bugs.launchpad.net/openconnect/+bug/2064028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064093] Re: if-up.d files do not have effect on ubuntu 24.04 LTS
Triggering if-up.d scripts changed completely without mention in documentation. For 23.10 scripts was triggered for each network interface separately. On boot it was with * PHASE=post-up, IFACE=lo; * PHASE=post-up, IFACE=virbr0; * PHASE=post-up, IFACE=enx047bcb671ca9; * PHASE=post-up, IFACE=docker0; * PHASE=post-up, IFACE=wlp0s20f3 Later on connecting to openconnect/anyconnect it was triggered with * PHASE=post-up, IFACE=vpn0 After upgrade to 24.04 it is triggered on boot only with: * PHASE=post-up, IFACE=lo; * PHASE=post-up, IFACE=-all Nothing triggered after connecting to openconnect/anyconnect https://bugs.launchpad.net/openconnect/+bug/2064028 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064093 Title: if-up.d files do not have effect on ubuntu 24.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/2064093/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064028] Re: after upgade ubuntu from 23.10 to 24.04 no if-up.d script are executed after connecting to openconnect vpn
** Summary changed: - after upgade ubuntu from 23.10 to 24.04 no if-up.d script are executed after connecting to openvpn + after upgade ubuntu from 23.10 to 24.04 no if-up.d script are executed after connecting to openconnect vpn ** Description changed: after upgade ubuntu from 23.10 to 24.04 no if-up.d script are executed after connecting to openvpn ProblemType: Bug DistroRelease: Ubuntu 24.04 - Package: openvpn 2.6.9-1ubuntu4 + Package: openconnect 9.12-1build5 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Apr 28 18:59:24 2024 InstallationDate: Installed on 2022-12-07 (508 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) SourcePackage: openvpn UpgradeStatus: Upgraded to noble on 2024-04-25 (3 days ago) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064028 Title: after upgade ubuntu from 23.10 to 24.04 no if-up.d script are executed after connecting to openconnect vpn To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvpn/+bug/2064028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064028] [NEW] after upgade ubuntu from 23.10 to 24.04 no if-up.d script are executed after connecting to openvpn
Public bug reported: after upgade ubuntu from 23.10 to 24.04 no if-up.d script are executed after connecting to openvpn ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: openvpn 2.6.9-1ubuntu4 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Apr 28 18:59:24 2024 InstallationDate: Installed on 2022-12-07 (508 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) SourcePackage: openvpn UpgradeStatus: Upgraded to noble on 2024-04-25 (3 days ago) ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064028 Title: after upgade ubuntu from 23.10 to 24.04 no if-up.d script are executed after connecting to openvpn To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2064028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930037] [NEW] BackInTime running as root doesn't backup anything, telling "no backup needed"
Public bug reported: 1) -- Description:Ubuntu 20.04.2 LTS Release:20.04 (same with Description:Ubuntu 21.04 Release:21.04 ) -- 2) backintime 1.2.1-2 -- 3) run backup as configured It is configured to backup whole /etc directory with Only default exclusions -- 4) after few seconds "no backup needed" message appears. Not even first ever snapshot is taken. Nothing is backed up even when I check "Take new snapshot regardless of there were changes or not" ** Affects: backintime (Ubuntu) Importance: Undecided Status: New ** Summary changed: - BackInTime running as root doesn't backup anythig claiming "no backup needed" + BackInTime running as root doesn't backup anything, telling "no backup needed" ** Description changed: - 1) + 1) -- Description: Ubuntu 20.04.2 LTS Release: 20.04 (same with Description: Ubuntu 21.04 - Release: 20.04 + Release: 21.04 ) -- - 2) + 2) backintime 1.2.1-2 -- 3) run backup as configured It is configured to backup whole /etc directory with Only default exclusions -- 4) after few seconds "no backup needed" message appears. Not even first ever snapshot is taken. Nothing is backed up even when I check "Take new snapshot regardless of there were changes or not" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930037 Title: BackInTime running as root doesn't backup anything, telling "no backup needed" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backintime/+bug/1930037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824874] Re: undismissable, unclickable authentication dialog left on screen (top-left corner) after policykit authentication [pushModal: invocation of begin_modal failed]
just got this on ubuntu 20.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824874 Title: undismissable, unclickable authentication dialog left on screen (top- left corner) after policykit authentication [pushModal: invocation of begin_modal failed] To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1824874/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892440] Re: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia)
Good job, it seems like packages from PPA fixed the issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892440 Title: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892440] Re: Shell text is too small in mutter 3.36.4-0ubuntu0.20.04.2
Extremely annoying bug. I need to set "Fonts"/"Scaling Factor" in Gnome Tweaks to 0.99 and back to 1.00 every time I re-/start my P52 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892440 Title: Shell text is too small in mutter 3.36.4-0ubuntu0.20.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769309] Re: Ubuntu 18.04 boot extremely slow
*** This bug is a duplicate of bug 1685794 *** https://bugs.launchpad.net/bugs/1685794 seems like the same problem is still there with Ubuntu 19.10 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769309 Title: Ubuntu 18.04 boot extremely slow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1769309/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1285444] Re: Login Successful, Desktop Never Loads
same here on P52, ubuntu 19.10, all completely updated to newest versions provided on official update sites. Additional reboot needed sometimes even more reboots -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1285444 Title: Login Successful, Desktop Never Loads To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1285444/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853117] Re: after update to 19.10 I am notified about new updates available even when there is none available
** Description changed: after update to ubuntu 19.10 I am notified about new updates available - on daily basis even when there is none available. + even when there is none available. It happens on daily basis. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-software 3.30.6-2ubuntu10 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Nov 19 09:52:18 2019 ExecutablePath: /usr/bin/gnome-software InstallationDate: Installed on 2019-07-11 (130 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) InstalledPlugins: - gnome-software-plugin-flatpak 3.30.6-2ubuntu10 - gnome-software-plugin-snap3.30.6-2ubuntu10 + gnome-software-plugin-flatpak 3.30.6-2ubuntu10 + gnome-software-plugin-snap3.30.6-2ubuntu10 SourcePackage: gnome-software UpgradeStatus: Upgraded to eoan on 2019-11-03 (15 days ago) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853117 Title: after update to 19.10 I am notified about new updates available even when there is none available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1853117/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853117] [NEW] after update to 19.10 I am notified about new updates available even when there is none available
Public bug reported: after update to ubuntu 19.10 I am notified about new updates available on daily basis even when there is none available. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-software 3.30.6-2ubuntu10 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Nov 19 09:52:18 2019 ExecutablePath: /usr/bin/gnome-software InstallationDate: Installed on 2019-07-11 (130 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) InstalledPlugins: gnome-software-plugin-flatpak 3.30.6-2ubuntu10 gnome-software-plugin-snap3.30.6-2ubuntu10 SourcePackage: gnome-software UpgradeStatus: Upgraded to eoan on 2019-11-03 (15 days ago) ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853117 Title: after update to 19.10 I am notified about new updates available even when there is none available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1853117/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850033] Re: Touchpad not working
Same here after upgrading ubuntu from 19.04 to 19.10 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850033 Title: Touchpad not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850033/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847896] Re: Unable to shutdown or restart from log-in screen
still there with ubuntu 19.10 everything & freshly upgraded -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847896 Title: Unable to shutdown or restart from log-in screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1847896/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851166] [NEW] extremely slow boot after upgrade to ubuntu 19.10, it takes ~2minutes to login screen
Public bug reported: after upgrade to ubuntu 19.10 I am facing extremely slow boot time it takes ~2minutes to login screen. I didn't check the time for 19.04 but it was something around 20-30seconds. Now after turning on notebook there is classical Ubuntu . boot screen for few second which disappears and black screen with blinking cursor in upper left corner remains most of the time(~100seconds). Then, after ~2minutes, login screen is shown. Lenovo P52, Intel Core i7-8750H 2,2GHz x 12, Quadro P1000/PCI2?SSE2, 32GB RWM ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-release-upgrader-core 1:19.10.15 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun Nov 3 21:30:44 2019 InstallationDate: Installed on 2019-07-11 (115 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to eoan on 2019-11-03 (0 days ago) VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851166 Title: extremely slow boot after upgrade to ubuntu 19.10, it takes ~2minutes to login screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1851166/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847921] Re: "iwlwifi 0000:04:00.0: Microcode SW error detected. Restarting 0x12000000." at boot
and dmesg ** Attachment added: "dmesg-5.3.0.19-18+lp1846016.out" https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1847921/+attachment/5299500/+files/dmesg-5.3.0.19-18+lp1846016.out -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847921 Title: "iwlwifi :04:00.0: Microcode SW error detected. Restarting 0x1200." at boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1847921/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847921] Re: "iwlwifi 0000:04:00.0: Microcode SW error detected. Restarting 0x12000000." at boot
Hi, I followed your instructions and installed 5.3.0-17.18+lp1846016. I didn't see any errors during boot just blinking cursor in left upper corner of display. However boot took probably same long time as when there were errors and, as I wrote, screen was black with blinking cursor instead of standard Ubuntu booting screen. I am attaching requested files "uname -a" output Linux p50 5.3.0-17-generic #18+lp1846016-Ubuntu SMP Fri Oct 4 14:18:23 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux ** Attachment added: "lspci-5.3.0.19-18+lp1846016.out" https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1847921/+attachment/5299499/+files/lspci-5.3.0.19-18+lp1846016.out -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847921 Title: "iwlwifi :04:00.0: Microcode SW error detected. Restarting 0x1200." at boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1847921/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847921] Re: "iwlwifi 0000:04:00.0: Microcode SW error detected. Restarting 0x12000000." at boot
still nothing offered as install candidate: corresponding line in apt update: Hit:3 http://ppa.launchpad.net/vicamo/ppa-1846016/ubuntu eoan InRelease installed packages containing "linux-" ii binutils-x86-64-linux-gnu 2.33-2ubuntu1 amd64GNU binary utilities, for x86-64-linux-gnu target ii liblinux-epoll-perl 0.016-1 amd64perl epoll module for O(1) multiplexing ii linux-base 4.5ubuntu2 all Linux image base package ii linux-firmware 1.183 all Firmware for Linux kernel drivers ii linux-generic 5.3.0.19.22 amd64Complete Generic Linux kernel and headers ii linux-headers-5.3.0-18 5.3.0-18.19 all Header files related to Linux kernel version 5.3.0 ii linux-headers-5.3.0-18-generic 5.3.0-18.19 amd64Linux kernel headers for version 5.3.0 on 64 bit x86 SMP ii linux-headers-5.3.0-19 5.3.0-19.20 all Header files related to Linux kernel version 5.3.0 ii linux-headers-5.3.0-19-generic 5.3.0-19.20 amd64Linux kernel headers for version 5.3.0 on 64 bit x86 SMP ii linux-headers-generic 5.3.0.19.22 amd64Generic Linux kernel headers ii linux-image-5.3.0-18-generic5.3.0-18.19+1 amd64Signed kernel image generic ii linux-image-5.3.0-19-generic5.3.0-19.20 amd64Signed kernel image generic ii linux-image-generic 5.3.0.19.22 amd64Generic Linux kernel image ii linux-libc-dev:amd645.3.0-19.20 amd64Linux Kernel Headers for development ii linux-modules-5.3.0-18-generic 5.3.0-18.19 amd64Linux kernel extra modules for version 5.3.0 on 64 bit x86 SMP ii linux-modules-5.3.0-19-generic 5.3.0-19.20 amd64Linux kernel extra modules for version 5.3.0 on 64 bit x86 SMP ii linux-modules-extra-5.3.0-18-generic5.3.0-18.19 amd64Linux kernel extra modules for version 5.3.0 on 64 bit x86 SMP ii linux-modules-extra-5.3.0-19-generic5.3.0-19.20 amd64Linux kernel extra modules for version 5.3.0 on 64 bit x86 SMP ii linux-signed-generic5.3.0.19.22 amd64Complete Signed Generic Linux kernel and headers (dummy transitional package) ii linux-sound-base 1.0.25+dfsg-0ubuntu5 all base package for ALSA and OSS sound systems ii syslinux-common 3:6.04~git20190206.bf6db5b4+dfsg1-1 all collection of bootloaders (common) ii syslinux-legacy 2:3.63+dfsg-2ubuntu9 amd64Bootloader for Linux/i386 using MS-DOS floppies "uname -a" output Linux p50 5.3.0-19-generic #20-Ubuntu SMP Fri Oct 18 09:04:39 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847921 Title: "iwlwifi :04:00.0: Microcode SW error detected. Restarting 0x1200." at boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1847921/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847921] Re: "iwlwifi 0000:04:00.0: Microcode SW error detected. Restarting 0x12000000." at boot
** Attachment added: "lspci output for 5.3.0.19 kernel" https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1847921/+attachment/5298943/+files/lspci-5.3.0.19.out -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847921 Title: "iwlwifi :04:00.0: Microcode SW error detected. Restarting 0x1200." at boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1847921/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847921] Re: "iwlwifi 0000:04:00.0: Microcode SW error detected. Restarting 0x12000000." at boot
Unfortunately, after adding your PPA no update is offered.. It is probably because I updated to official 5.3.0.19 kernel earlier today... problem remains the same. I am attaching new dmesg & lspci ** Attachment added: "dmesg output for 5.3.0.19 kernel" https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1847921/+attachment/5298942/+files/dmesg-5.3.0.19.out -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847921 Title: "iwlwifi :04:00.0: Microcode SW error detected. Restarting 0x1200." at boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1847921/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847921] Re: "iwlwifi 0000:04:00.0: Microcode SW error detected. Restarting 0x12000000." at boot
and lspci output, I hope it could help ** Attachment added: "lspci.out" https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1847921/+attachment/5298266/+files/lspci.out -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847921 Title: "iwlwifi :04:00.0: Microcode SW error detected. Restarting 0x1200." at boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1847921/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847921] Re: "iwlwifi 0000:04:00.0: Microcode SW error detected. Restarting 0x12000000." at boot
here dmesg output ** Attachment added: "dmesg.out" https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1847921/+attachment/5298265/+files/dmesg.out -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847921 Title: "iwlwifi :04:00.0: Microcode SW error detected. Restarting 0x1200." at boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1847921/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847921] [NEW] "iwlwifi 0000:04:00.0: Microcode SW error detected. Restarting 0x12000000." at boot
Public bug reported: however after this and waiting a minute it turns on and everything seems to work(including wifi connection) wifi controllers seems to be: Intel Corporation Wireless-AC 9650 [Jefferson Peak] (rev 10) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-firmware 1.183 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 13 18:57:16 2019 Dependencies: InstallationDate: Installed on 2018-04-27 (533 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: Upgraded to eoan on 2019-10-13 (0 days ago) ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847921 Title: "iwlwifi :04:00.0: Microcode SW error detected. Restarting 0x1200." at boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1847921/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1833749] [NEW] unfocused terminal window blinking because of transparency unreasonably changing
Public bug reported: unfocused terminal window blinking because of transparency unreasonably changing without any action on keyboard nor mouse ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8 Uname: Linux 5.0.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 418.56 Fri Mar 15 12:59:26 CDT 2019 GCC version: gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1) ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 21 20:01:45 2019 DistUpgraded: 2019-04-19 17:34:11,213 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: disco DistroVariant: ubuntu DkmsStatus: nvidia, 418.56, 5.0.0-16-generic, x86_64: installed nvidia, 418.56, 5.0.0-17-generic, x86_64: installed virtualbox, 6.0.6, 5.0.0-16-generic, x86_64: installed virtualbox, 6.0.6, 5.0.0-17-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: NVIDIA Corporation GM107GLM [Quadro M2000M] [10de:13b0] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Lenovo GM107GLM [Quadro M2000M] [17aa:2230] InstallationDate: Installed on 2018-04-27 (420 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 20EN0008XS ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-17-generic root=UUID=9ba5bcf6-c098-48cd-b443-cbb9ab3b0f03 ro quiet splash acpi_sleep=nonvs vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to disco on 2019-04-19 (63 days ago) dmi.bios.date: 02/21/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1EET83W (1.56 ) dmi.board.asset.tag: Not Available dmi.board.name: 20EN0008XS dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1EET83W(1.56):bd02/21/2019:svnLENOVO:pn20EN0008XS:pvrThinkPadP50:rvnLENOVO:rn20EN0008XS:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P50 dmi.product.name: 20EN0008XS dmi.product.sku: LENOVO_MT_20EN_BU_Think_FM_ThinkPad P50 dmi.product.version: ThinkPad P50 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 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 disco third-party-packages ubuntu ** Attachment added: "terminal-transparency-unreasonably-changing" https://bugs.launchpad.net/bugs/1833749/+attachment/5272172/+files/terminal-transparency-unreasonably-changing.mp4 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1833749 Title: unfocused terminal window blinking because of transparency unreasonably changing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1833749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1791219] Re: Symbolic link to src.zip in openjdk-11-source points to an invalid location
the same bug in openjdk-10 and openjdk-12 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1791219 Title: Symbolic link to src.zip in openjdk-11-source points to an invalid location To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjdk-lts/+bug/1791219/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825547] Re: incorrect vpn status
GNOME 3.32.1 GNOME Shell 3.32.0 I know about fix for 18.10, I was facing this issue that time already and was happy with the fix. However right after upgrade to 19.04 the problem was here again but I didn't take screenshot. Then it behave correct for few days and now/today the issue is back again so I added screenshot. Unfortunately I am not able to identify anything more about the issue -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825547 Title: incorrect vpn status To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1825547/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825547] Re: old bug "nm-applet stop showing vpn status" is back
** Changed in: gnome-shell (Ubuntu) Status: Invalid => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825547 Title: old bug "nm-applet stop showing vpn status" is back To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1825547/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825547] Re: old bug "nm-applet stop showing vpn status" is back
somehow the situation appeared again, I have no idea what is cause of the status but I was able to make screenshot now ** Attachment added: "Screenshot from 2019-04-30 11-04-38.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1825547/+attachment/5260236/+files/Screenshot%20from%202019-04-30%2011-04-38.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825547 Title: old bug "nm-applet stop showing vpn status" is back To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1825547/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825547] Re: old bug "nm-applet stop showing vpn status" is back
Hi there, I am not sure if there was some update in a mean time however now it seems to work correctly. ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825547 Title: old bug "nm-applet stop showing vpn status" is back To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1825547/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825547] Re: old bug "nm-applet stop showing vpn status" is back
I am not sure how to close this issue correctly so I changed status to "invalid" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825547 Title: old bug "nm-applet stop showing vpn status" is back To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1825547/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825547] Re: old bug "nm-applet stop showing vpn status" is back
** Description changed: old bug #1756720 "nm-applet stop showing vpn status" is back after upgrade to Ubuntu 19.04 - --- + --- + + 1. The specific steps or actions you took that caused you to encounter + the problem. + + Connect to any VPN. Connection is open. + + + 2. The behavior you expected. + + VPN connection should be displayed as connected in + "Settings->Network->VPN" as well as in nm-applet (upper right corner of + display) + + + 3. The behavior you actually encountered (in as much detail as possible). + + In "Settings->Network->VPN" it is shown as open but in nm-applet + as closed. + + --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2018-04-27 (361 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.32.0+git20190410-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Tags: disco third-party-packages Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-04-19 (4 days ago) UserGroups: adm cdrom dialout dip docker libvirt lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825547 Title: old bug "nm-applet stop showing vpn status" is back To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1825547/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825547] Re: old bug "nm-applet stop showing vpn status" is back
apport information ** Tags added: apport-collected third-party-packages ** Description changed: - old bug #1756720 "nm-applet stop showing vpn status" is back after - upgrade to Ubuntu 19.04 + old bug #1756720 "nm-applet stop showing vpn status" is back after upgrade to Ubuntu 19.04 + --- + ProblemType: Bug + ApportVersion: 2.20.10-0ubuntu27 + Architecture: amd64 + CurrentDesktop: ubuntu:GNOME + DisplayManager: gdm3 + DistroRelease: Ubuntu 19.04 + InstallationDate: Installed on 2018-04-27 (361 days ago) + InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) + NonfreeKernelModules: nvidia_modeset nvidia + Package: gnome-shell 3.32.0+git20190410-1ubuntu1 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 + Tags: disco third-party-packages + Uname: Linux 5.0.0-13-generic x86_64 + UpgradeStatus: Upgraded to disco on 2019-04-19 (4 days ago) + UserGroups: adm cdrom dialout dip docker libvirt lpadmin plugdev sambashare sudo vboxusers + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1825547/+attachment/5258349/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825547 Title: old bug "nm-applet stop showing vpn status" is back To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1825547/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825547] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1825547/+attachment/5258352/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825547 Title: old bug "nm-applet stop showing vpn status" is back To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1825547/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825547] GsettingsChanges.txt
apport information ** Attachment added: "GsettingsChanges.txt" https://bugs.launchpad.net/bugs/1825547/+attachment/5258350/+files/GsettingsChanges.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825547 Title: old bug "nm-applet stop showing vpn status" is back To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1825547/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825547] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1825547/+attachment/5258351/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825547 Title: old bug "nm-applet stop showing vpn status" is back To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1825547/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1756720] Re: nm-applet stop showing vpn status
this bug seems to be back with release of Ubuntu19.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1756720 Title: nm-applet stop showing vpn status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1756720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825547] [NEW] old bug "nm-applet stop showing vpn status" is back
Public bug reported: old bug #1756720 "nm-applet stop showing vpn status" is back after upgrade to Ubuntu 19.04 ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Description changed: old bug #1756720 "nm-applet stop showing vpn status" is back after - upgrade to release of Ubuntu 19.04 + upgrade to Ubuntu 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/1825547 Title: old bug "nm-applet stop showing vpn status" is back To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1825547/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1812266] Re: Keyboard layout indicator does not indicate current layout (18.04 Bionic beaver)
Still there with Ubuntu 18.10 after first lock + unlock screen. Fresh update/upgrade and restart right now: ii gnome-shell 3.30.1-2ubuntu1.18.10.2 amd64graphical shell for the GNOME desktop ii gnome-shell-common 3.30.1-2ubuntu1.18.10.2 all common files for the GNOME graphical shell -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1812266 Title: Keyboard layout indicator does not indicate current layout (18.04 Bionic beaver) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812266/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1801189] Re: After upgrade from 18.04 to 18.10 no hosts are resolved from DNS configured in VPN connection
unfortunately I am not able to recognize what package is the bug related to... it is probably one of dnsmasq, network-manager-openconnect-gnome, network-manager-openconnect, openconnect, resolvconf ** Package changed: ubuntu => network-manager-openconnect (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1801189 Title: After upgrade from 18.04 to 18.10 no hosts are resolved from DNS configured in VPN connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openconnect/+bug/1801189/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1801189] Re: After upgrade from 18.04 to 18.10 no hosts are resolved from DNS configured in VPN connection
** Description changed: After upgrade from 18.04 to 18.10 when I am connected to a cisco- anyconnect-compatible VPN, no hosts are resolved from DNS configured in VPN connection. error entry from syslog: "systemd-resolved: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP." + + really simple configuration: only gateway set when creating, later when + connecting I enter username and password. All other settings left + default. + + after successful connection + run "nslookup " doesn't resolve anything + run "nslookup " resolves IP correctly + + is "behind" VPN so request is routed correctly to VPN -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1801189 Title: After upgrade from 18.04 to 18.10 no hosts are resolved from DNS configured in VPN connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1801189/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1801189] [NEW] After upgrade from 18.04 to 18.10 no hosts are resolved from DNS configured in VPN connection
Public bug reported: After upgrade from 18.04 to 18.10 when I am connected to a cisco- anyconnect-compatible VPN, no hosts are resolved from DNS configured in VPN connection. error entry from syslog: "systemd-resolved: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP." really simple configuration: only gateway set when creating, later when connecting I enter username and password. All other settings left default. after successful connection run "nslookup " doesn't resolve anything run "nslookup " resolves IP correctly is "behind" VPN so request is routed correctly to VPN ** Affects: ubuntu Importance: Undecided Status: New ** Description changed: After upgrade from 18.04 to 18.10 when I am connected to a cisco- anyconnect-compatible VPN, no hosts are resolved from DNS configured in VPN connection. error entry from syslog: "systemd-resolved: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP." - - any ideas what is the problem and how to fix/workaround it? - thank you -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1801189 Title: After upgrade from 18.04 to 18.10 no hosts are resolved from DNS configured in VPN connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1801189/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1692079] Re: Can't grab message list scrollbar
same here Thunderbird 52.9.1, Ubuntu 18.04.1, Gnome 3.28.2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1692079 Title: Can't grab message list scrollbar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1692079/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1716982] Re: Dash to Dock still visible on lock screen under gnome-shell
I can confirm. This is not fixed in 18.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1716982 Title: Dash to Dock still visible on lock screen under gnome-shell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1716982/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767804] [NEW] emoji icons too large, not of font size
Public bug reported: emoji icons are too large, not of font size. It is probably most annoying in thunderbird and mail subject. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: fonts-noto-color-emoji 0~20180424-0ubuntu1 [modified: usr/share/fonts/truetype/noto/NotoColorEmoji.ttf] ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 29 15:32:11 2018 Dependencies: InstallationDate: Installed on 2018-04-27 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: fonts-noto-color-emoji UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: fonts-noto-color-emoji (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "large emojis example in thunderbird" https://bugs.launchpad.net/bugs/1767804/+attachment/5130149/+files/large-emojis-in-subjects-thunderbird.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767804 Title: emoji icons too large, not of font size To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-noto-color-emoji/+bug/1767804/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1721428] Re: Artful (17.10) Session logout after screen turned off
Actually logout can occur without any cable manipulation or turning on/off external monitor. Few times it already happened to me with just lock screen activated. No standby, no hibernate. After I came back, I expected a screen to enter password for unlock, but login screen appear... Means session was logged out and all work lost... No restart was made concerning uptime result... My config: Lenovo P50, noveau driver for nvidia, Ubuntu17.10, everything updated to most recent versions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1721428 Title: Artful (17.10) Session logout after screen turned off To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1721428/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1661486] Re: nouveau write fault, CTXSW_TIMEOUT, hangs the display
same problem here. System freezes completely(except, I can move mouse pointer. Just move, no click) and after restart buch of "nouveau :01:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT]" in syslog. ubuntu 16.04, 4.4.0-78-generic #99-Ubuntu SMP, Lenovo P50. I cannot switch to nvidia-XXX driver as it is unusable in multiple monitors configuration. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1661486 Title: nouveau write fault, CTXSW_TIMEOUT, hangs the display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1661486/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1575248] Re: "AppStream cache update completed, but some metadata was ignored due to errors." on "sudo apt-get update"
same here as of Friday(25th November 2016) update -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1575248 Title: "AppStream cache update completed, but some metadata was ignored due to errors." on "sudo apt-get update" To manage notifications about this bug go to: https://bugs.launchpad.net/appstream/+bug/1575248/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1562335] Re: Multidisplay configuration randomly/unpredictably changes with each boot or return from screen-lock(screen-dim)
** Summary changed: - Multidisplay configuration randomly/unpredictably changes with each boot or screen-lock(screen-dim) recovery + Multidisplay configuration randomly/unpredictably changes with each boot or return from screen-lock(screen-dim) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1562335 Title: Multidisplay configuration randomly/unpredictably changes with each boot or return from screen-lock(screen-dim) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1562335/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 364091] Re: xrandr error with delmode
In case this bug was solved, it is back here in Ubuntu15.10 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/364091 Title: xrandr error with delmode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/x11-xserver-utils/+bug/364091/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1562335] Re: Multidisplay configuration randomly/unpredictably changes with each boot or screen-lock(screen-dim) recovery
** Description changed: - Multidisplay configuration randomly/unpredictably changes with each boot or screen-unlock. - My configuration is thinkpad P50 with intel/nvidia hybrid display adapters. "Internal" high-dpi 3840x2160px + "External" high-dpi 3840x2160px displays. - Configuration which I am trying to achieve is: both monitors in 1920x1080px mode configured as extended desktop. This is mostly possible to achieve using "Displays" tool even there are some strange behavior(for example changing rotation of display when only switching resolution) - After almost each(let say 80%) boot and screen-unlock are display settings randomly/unpredictably changed. + Multidisplay configuration randomly/unpredictably changes with each boot + or screen-unlock. + + My hardware configuration is thinkpad P50 with intel/nvidia hybrid + display adapters. "Internal" high-dpi 3840x2160px + "External" high-dpi + 3840x2160px displays. + + Multidisplay configuration which I am trying to achieve is: both + monitors in 1920x1080px mode configured as extended desktop. I am mostly + able to achieve it using "Displays" tool even there is some strange + behavior(for example changing rotation of display when only switching + resolution) + + Problem: after almost each(let say 80%) boot and screen-unlock are display settings randomly/unpredictably changed and I have to do all displays setup again or even to restart lightdm. This is a bit curious as after boot, the setup is mostly misconfigured bud after restart only lightdm service it is much more often correct. + One important think is that this misconfiguration happend after login, greeter seems to be setup correct after almost each reboot or lightdm restart. Login is followed by some unwanted/unnecessary blinking and display modes switching which ends as misconfiguration mostly. Some examples: - both or one of monitor is set to native 3840x2160px resolution - mirroring is set instead of extended desktop - - if kept in last correct 1920x1080px resolution then some weird panning is applied for one of displays - + - if kept in last correct 1920x1080px resolution then some weird panning is applied for one or both displays - the same behavior occurs using any nvidia-XXX driver available in ubuntu or launchpad repositories. - nouveau driver seems to not support any multidisplay configuration - Description: Ubuntu 15.10 Release: 15.10 ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: lightdm 1.16.7-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4 Uname: Linux 4.2.0-34-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Sat Mar 26 16:22:26 2016 InstallationDate: Installed on 2016-03-25 (0 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1562335 Title: Multidisplay configuration randomly/unpredictably changes with each boot or screen-lock(screen-dim) recovery To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1562335/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1562335] [NEW] Multidisplay configuration randomly/unpredictably changes with each boot or screen-lock(screen-dim) recovery
Public bug reported: Multidisplay configuration randomly/unpredictably changes with each boot or screen-unlock. My configuration is thinkpad P50 with intel/nvidia hybrid display adapters. "Internal" high-dpi 3840x2160px + "External" high-dpi 3840x2160px displays. Configuration which I am trying to achieve is: both monitors in 1920x1080px mode configured as extended desktop. This is mostly possible to achieve using "Displays" tool even there are some strange behavior(for example changing rotation of display when only switching resolution) After almost each(let say 80%) boot and screen-unlock are display settings randomly/unpredictably changed. Some examples: - both or one of monitor is set to native 3840x2160px resolution - mirroring is set instead of extended desktop - if kept in last correct 1920x1080px resolution then some weird panning is applied for one of displays - the same behavior occurs using any nvidia-XXX driver available in ubuntu or launchpad repositories. - nouveau driver seems to not support any multidisplay configuration Description:Ubuntu 15.10 Release:15.10 ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: lightdm 1.16.7-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4 Uname: Linux 4.2.0-34-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Sat Mar 26 16:22:26 2016 InstallationDate: Installed on 2016-03-25 (0 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wily -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1562335 Title: Multidisplay configuration randomly/unpredictably changes with each boot or screen-lock(screen-dim) recovery To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1562335/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1379084] Re: After updating ubuntu using software updater built-in notebook display in multi-display configuration keeps showing boot screen
the problem becomes showstopper in 15.10 and 4K display on pure new installation on Thinkpad P50 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1379084 Title: After updating ubuntu using software updater built-in notebook display in multi-display configuration keeps showing boot screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1379084/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1543893] [NEW] crash on automatically partitioning whole system while installing
Public bug reported: crash on automatically partitioning whole system while installing ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: ubiquity 2.21.37 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 CasperVersion: 1.365 Date: Wed Feb 10 02:35:27 2016 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity cdrom-detect/try-usb=true noprompt floppy.allowed_drive_mask=0 ignore_uuid initrd=/casper/initrd.lz quiet splash --- BOOT_IMAGE=/casper/vmlinuz.efi LiveMediaBuild: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ubiquity-2.21.37 ubuntu wily -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1543893 Title: crash on automatically partitioning whole system while installing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1543893/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 686859] Re: "Bootloader install failed" cannot be closed
Still there for 15.10 After doing anything in "Bootloader install failed" dialog, the OK button is always clickable however nothing will happen... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/686859 Title: "Bootloader install failed" cannot be closed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/686859/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1379084] Re: After updating ubuntu using software updater built-in notebook display in multi-display configuration keeps showing boot screen
problem seems to be in package ubuntu-drivers-common... upgrading it from v0.2.91.5 to v0.2.91.6 from trusty-proposed repo on Jun 27th caused the same problem as upgrading it from v0.2.91.5 to v0.2.91.7 from trusty-updates this time I was only able to downgrade it to v0.2.91.4 using synaptics. However, problem is gone... Everythig works fine now... ** Package changed: unity (Ubuntu) = ubuntu-drivers-common (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1379084 Title: After updating ubuntu using software updater built-in notebook display in multi-display configuration keeps showing boot screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1379084/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1379084] Re: After updating ubuntu using software updater built-in notebook display in multi-display configuration keeps showing boot screen
history of my ubuntu-drivers-common(I double checked to downgrade and upgrade only this package) ** Attachment added: Screenshot from 2014-10-10 00:57:16.png https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1379084/+attachment/4230136/+files/Screenshot%20from%202014-10-10%2000%3A57%3A16.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1379084 Title: After updating ubuntu using software updater built-in notebook display in multi-display configuration keeps showing boot screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1379084/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1379084] [NEW] After updating ubuntu using software updater built-in notebook display in multi-display configuration keeps showing boot screen
Public bug reported: After recent update of Ubuntu 14.04LTS using software updater built-in notebook display in multi-display configuration keeps showing boot screen(or splash screen) after power-on/restart. Problem is fixed after I turn the display off and on afterwards using System Settings-Displays. I found the problem few months ago in trusty-proposed repository updates. After I uninstalled all proposed it was fixed again. Problem was moved to standard updates now. http://askubuntu.com/questions/490555 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.2+14.04.20140714-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.38 Wed Jan 8 19:32:30 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Oct 9 03:29:57 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21d1] NVIDIA Corporation GF119M [Quadro NVS 4200M] [10de:1057] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21d1] InstallationDate: Installed on 2014-05-15 (146 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: LENOVO 42404JG ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic root=UUID=bdc9fa6a-b11c-4d99-a6e1-39117631e049 ro quiet splash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/26/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 8AET64WW (1.44 ) dmi.board.asset.tag: Not Available dmi.board.name: 42404JG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8AET64WW(1.44):bd07/26/2013:svnLENOVO:pn42404JG:pvrThinkPadT520:rvnLENOVO:rn42404JG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 42404JG dmi.product.version: ThinkPad T520 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Thu Oct 9 01:32:04 2014 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 16562 vendor LEN xserver.version: 2:1.15.1-0ubuntu2.1 ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 third-party-packages trusty ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1379084 Title: After updating ubuntu using software updater built-in notebook display in multi-display configuration keeps showing boot screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1379084/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1003813] Re: Kernel Oops during mount.cifs (CIFS VFS: could not allocate crypto hmacmd5)
same critical error after updating to 3.2.0-49-generic #75-Ubuntu SMP Tue Jun 18 17:39:32 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux dmesg: [ 87.218051] CIFS VFS: could not allocate crypto hmacmd5 [ 87.218053] [ 87.218054] CIFS VFS: could not allocate crypto hmacmd5 [ 87.218055] [ 87.218057] CIFS VFS: could not setup hash structures rc -2 [ 87.218059] general protection fault: [#1] SMP [ 87.218061] CPU 2 [ 87.218063] Modules linked in: [ 87.218064] CIFS VFS: could not setup hash structures rc -110 [ 87.218066] vmnet(O) vsock(O) vmci(O) vmmon(O) nls_utf8 cifs rfcomm bnep snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_intel joydev snd_hda_codec snd_hwdep snd_pcm snd_seq_midi snd_rawmidi snd_seq_midi_event video snd_seq snd_timer snd_seq_device nvidia(P) eeepc_wmi asus_wmi sparse_keymap snd btusb bluetooth binfmt_misc mac_hid wmi mei(C) soundcore snd_page_alloc ppdev psmouse serio_raw parport_pc lp parport usbhid hid r8169 [ 87.218098] [ 87.218100] Pid: 1328, comm: mount.cifs Tainted: P C O 3.2.0-49-generic #75-Ubuntu System manufacturer System Product Name/P8H77-M PRO [ 87.218103] RIP: 0010:[812df5db] [812df5db] crypto_larval_kill+0x2b/0x90 [ 87.218108] RSP: 0018:880402b0db68 EFLAGS: 00010296 [ 87.218109] RAX: dead00200200 RBX: 880402b52000 RCX: c100 [ 87.218110] RDX: dead00100100 RSI: 0286 RDI: 81c63b80 [ 87.218111] RBP: 880402b0db78 R08: 880402b0c000 R09: 0004 [ 87.218112] R10: R11: 0001 R12: ff92 [ 87.218113] R13: a0bd7f78 R14: R15: 880403a8c500 [ 87.218115] FS: 7f5723e24700() GS:88041ec8() knlGS: [ 87.218116] CS: 0010 DS: ES: CR0: 8005003b [ 87.218125] CR2: 04160ff0 CR3: 000403258000 CR4: 001406e0 [ 87.218126] DR0: DR1: DR2: [ 87.218127] DR3: DR6: 0ff0 DR7: 0400 [ 87.218129] Process mount.cifs (pid: 1328, threadinfo 880402b0c000, task 880403a8c500) [ 87.218130] Stack: [ 87.218138] 880402b52000 ff92 880402b0db98 812dfe3b [ 87.218141] 81838480 880402b0dbe8 812e007d [ 87.218142] 880402b0dc08 a0bbcb36 880402b0dc08 880402298400 [ 87.218144] Call Trace: [ 87.218147] [812dfe3b] crypto_alg_mod_lookup+0x6b/0x90 [ 87.218148] [812e007d] crypto_alloc_tfm+0x6d/0xe0 [ 87.218153] [a0bbcb36] ? cifs_convert_address+0x46/0x120 [cifs] [ 87.218156] [812e6fe9] crypto_alloc_shash+0x19/0x20 [ 87.218160] [a0bc2181] cifs_crypto_shash_allocate+0x21/0x1a0 [cifs] [ 87.218163] [a0ba8e96] cifs_get_tcp_session+0x126/0x6a0 [cifs] [ 87.218166] [a0bae09d] cifs_mount+0x8d/0x5f0 [cifs] [ 87.218168] [a0b9b991] ? cifs_do_mount+0x91/0x280 [cifs] [ 87.218170] [a0b9b9b5] cifs_do_mount+0xb5/0x280 [cifs] [ 87.218173] [8117dae3] mount_fs+0x43/0x1b0 [ 87.218176] [811984ca] vfs_kern_mount+0x6a/0xc0 [ 87.218178] [811999d4] do_kern_mount+0x54/0x110 [ 87.218180] [8119b534] do_mount+0x1a4/0x260 [ 87.218182] [8119ba10] sys_mount+0x90/0xe0 [ 87.218185] [816686c2] system_call_fastpath+0x16/0x1b [ 87.218185] Code: 55 48 89 e5 53 48 83 ec 08 0f 1f 44 00 00 48 89 fb 48 c7 c7 80 3b c6 81 e8 43 fd 37 00 48 8b 13 48 8b 43 08 48 c7 c7 80 3b c6 81 48 89 42 08 48 89 10 48 b8 00 01 10 00 00 00 ad de 48 ba 00 02 [ 87.218201] RIP [812df5db] crypto_larval_kill+0x2b/0x90 [ 87.218203] RSP 880402b0db68 [ 87.218205] ---[ end trace 1065cb24c0d00d23 ]--- [ 87.218273] CIFS VFS: cifs_mount failed w/return code = -2 [ 87.218300] CIFS VFS: cifs_mount failed w/return code = -110 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1003813 Title: Kernel Oops during mount.cifs (CIFS VFS: could not allocate crypto hmacmd5) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cifs-utils/+bug/1003813/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1003813] Re: Kernel Oops during mount.cifs (CIFS VFS: could not allocate crypto hmacmd5)
same critical error after updating to 3.2.0-38-generic #61-Ubuntu SMP Tue Feb 19 12:18:21 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux With previous version it was OK -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1003813 Title: Kernel Oops during mount.cifs (CIFS VFS: could not allocate crypto hmacmd5) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cifs-utils/+bug/1003813/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 951087] Re: Samba non-functional on boot.
** Changed in: samba (Ubuntu) Status: Expired = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/951087 Title: Samba non-functional on boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/951087/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 996968] Re: Samba needs to be stopped and restarted in order to work
confirmed on fresh install of ubuntu 12.04TLS, it is definitely not dependent on PArnal's local configuration, for me even start on (local-filesystems and net-device-up IFACE=eth0) did not help it needs restart of smbd/nmbd after each reboot ** Changed in: samba (Ubuntu) Status: Invalid = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/996968 Title: Samba needs to be stopped and restarted in order to work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/996968/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 951087] Re: Samba non-functional on boot.
the bug is still here... confirmed again on fresh install of Ubuntu 12.04LTS even start on (local-filesystems and net-device-up IFACE=eth0) did not help -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/951087 Title: Samba non-functional on boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/951087/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 951087] Re: Samba non-functional on boot.
** Changed in: samba (Ubuntu) Status: Expired = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/951087 Title: Samba non-functional on boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/951087/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 951087] Re: Samba non-functional on boot.
the bug is still here... confirmed again on fresh install of Ubuntu 12.04LTS even start on (local-filesystems and net-device-up IFACE=eth0) did not help -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/951087 Title: Samba non-functional on boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/951087/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 996968] Re: Samba needs to be stopped and restarted in order to work
confirmed on fresh install of ubuntu 12.04TLS, it is definitely not dependent on PArnal's local configuration, for me even start on (local-filesystems and net-device-up IFACE=eth0) did not help it needs restart of smbd/nmbd after each reboot ** Changed in: samba (Ubuntu) Status: Invalid = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/996968 Title: Samba needs to be stopped and restarted in order to work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/996968/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
