[Bug 2078555] Re: Upgrading from 22.04 to 24.04.01 breaks dnsmasq
At this point, i fully expect for the systemd team to not lift a finger as usual and i'm going to run into this major bug again in a couple of years when upgrading to 26.04... :-( -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078555 Title: Upgrading from 22.04 to 24.04.01 breaks dnsmasq To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2078555/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078851] Re: saslauthd wrong permission of /var/spool/postfix/var/run/saslauthd
Bryce, just for clarification: saslauthd starts just fine without the fix, but postfix will be unable to authenticate because it can't communicate with saslauthd. This effectively prevents outgoing mail submitted via smtp. It used to work fine on previous LTS release, upgrading to 24.04 broke it because the standard service config now nukes the permissions on every service start. On my system, the upgrade from 22.04 to 24.04 effectively turned into a "denial of service" for outgoing mail until i put in my workaround. So this affects existing servers that are going to be upgraded. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078851 Title: saslauthd wrong permission of /var/spool/postfix/var/run/saslauthd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/2078851/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078851] Re: saslauthd wrong permission of /var/spool/postfix/var/run/saslauthd
Will there be a fix for 24.04/Noble as well? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078851 Title: saslauthd wrong permission of /var/spool/postfix/var/run/saslauthd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/2078851/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078555] Re: Upgrading from 22.04 to 24.04.01 breaks dnsmasq
"but this may be the right behavior, to install systemd-resolved" In my case, systemd-resolved was installed before the upgrade, but it was disables via command line. On updates and upgrades, i expect the package manager to respect the configuration choices that have been made previously. do-release-upgrade asked a gazillion other questions if it should keep a configuration or update it with the maintainers version. It *could* have asked "Hey, i'm upgrading a service that's disabled. Do you want to a) re-enable it, b) keep it disabled c) uninstall it completely". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078555 Title: Upgrading from 22.04 to 24.04.01 breaks dnsmasq To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2078555/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078852] Re: systemd-resolved was re-enabled during upgrade from 22.04 to 24.04
See also bug 2078555 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078852 Title: systemd-resolved was re-enabled during upgrade from 22.04 to 24.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2078852/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078555] Re: Upgrading from 22.04 to 24.04.01 breaks dnsmasq
I'm running a different DNS solution, but i'm running into the same problem with systemd-resolved See bug 2078852 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078555 Title: Upgrading from 22.04 to 24.04.01 breaks dnsmasq To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2078555/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078852] [NEW] systemd-resolved was re-enabled during upgrade from 22.04 to 24.04
Public bug reported: systemd-resolved was disabled on my servers because i use a different DNS setup. During upgrade from 22.04 to 24.04, systemd-resolved was re-enabled by the upgrade process. This would have lead to downtime of some services as well other problems, because local DNS lookups failed to use the correct server. Re-enabling systemd-resolved also overwrote /etc/resolv.conf, which had to be restored from backups. This has now been a so long standing problem (going back many LTS releases) that i have a script for that called the "systemd-castrator". It basically does: systemctl disable systemd-resolved systemctl stop systemd-resolved and then restores the correct resolv.conf from my source code management. It would be nice if this problem could be solved by the Ubuntu team. E.g. "if a systemd service is manually disabled before the upgrade, it *stays* disabled after the upgrade". ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: systemd-resolved 255.4-1ubuntu8.4 ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12 Uname: Linux 6.8.0-41-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Sep 3 20:00:16 2024 SourcePackage: systemd UpgradeStatus: Upgraded to noble on 2024-08-31 (3 days ago) mtime.conffile..etc.init.d.apport: 2024-07-22T16:59:07 ** Affects: systemd (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/2078852 Title: systemd-resolved was re-enabled during upgrade from 22.04 to 24.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2078852/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078851] [NEW] saslauthd wrong permission of /var/spool/postfix/var/run/saslauthd
Public bug reported: Folder group permission of /var/spool/postfix/var/run/saslauthd gets reset to "root" (should be "sasl") every time saslauthd gets restarted. This worked fine before upgrading from 22.04 to 24.04 My automated workaround currently is this crontab (root) entry: */1 * * * * /usr/bin/chgrp sasl /var/spool/postfix/var/run/saslauthd 2>&1 ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: postfix 3.8.6-1build2 ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12 Uname: Linux 6.8.0-41-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Sep 3 19:52:59 2024 SourcePackage: postfix UpgradeStatus: Upgraded to noble on 2024-08-31 (3 days ago) mtime.conffile..etc.init.d.apport: 2024-07-22T16:59:07 ** Affects: postfix (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/2078851 Title: saslauthd wrong permission of /var/spool/postfix/var/run/saslauthd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/2078851/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067207] [NEW] on kubuntu 24.04, keyboard specialized keys for volume control no longer work
Public bug reported: please, when you can, do look into this troublesome little issue. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: pulseaudio 1:16.1+dfsg1-2ubuntu10 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: unknown CurrentDesktop: KDE Date: Sun May 26 14:33:53 2024 InstallationDate: Installed on 2024-05-25 (1 days ago) InstallationMedia: Kubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240425.1) MachineType: ASUS System Product Name PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/10/2022 dmi.bios.release: 4.20 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0420 dmi.board.asset.tag: Default string dmi.board.name: ROG CROSSHAIR X670E EXTREME dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0420:bd08/10/2022:br4.20:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGCROSSHAIRX670EEXTREME:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS ** Affects: pulseaudio (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/2067207 Title: on kubuntu 24.04, keyboard specialized keys for volume control no longer work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2067207/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969274] [NEW] openvpn client no longer connects in 22.04
Public bug reported: Client no longer connects. previous version had no problem ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: network-manager-openvpn 1.8.18-1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Apr 16 15:09:56 2022 InstallationDate: Installed on 2022-04-15 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) SourcePackage: network-manager-openvpn UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: network-manager-openvpn (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969274 Title: openvpn client no longer connects in 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1969274/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1579268] Re: Mouse cursor is different inside graphical windows of snaps (snaps not using system theme)
I just upgraded to 21.10, and it affects the Firefox from Snap if FF isn't using the automatic system theme extension. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1579268 Title: Mouse cursor is different inside graphical windows of snaps (snaps not using system theme) To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1579268/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900472] Re: [snap] Mouse pointer scaling issue
*** This bug is a duplicate of bug 1900334 *** https://bugs.launchpad.net/bugs/1900334 ** Also affects: firefox (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/1900472 Title: [snap] Mouse pointer scaling issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1900472/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916651] Re: asks about irc user home directory during upgrade
Had the same issue but installed and removed "teamviewer" a view days before upgrading to 21.04. Could user "irc" being left from this former program installation? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916651 Title: asks about irc user home directory during upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-passwd/+bug/1916651/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915688] [NEW] Please enable CONFIG_FANOTIFY_ACCESS_PERMISSIONS
Public bug reported: The CONFIG_FANOTIFY_ACCESS_PERMISSIONS option is required for certain security products, like Microsoft Defender for Endpoints, to operate correctly. As far as I can tell, it causes no overhead (when not actively using it), in terms of code size or startup time. It is currently disabled in the Focal Fossa -kvm kernel: $ grep CONFIG_FANOTIFY /boot/config-5.4.0-1032-kvm CONFIG_FANOTIFY=y # CONFIG_FANOTIFY_ACCESS_PERMISSIONS is not set While it is enabled in the -generic kernel: $ grep CONFIG_FANOTIFY /boot/config-5.4.0-65-generic CONFIG_FANOTIFY=y CONFIG_FANOTIFY_ACCESS_PERMISSIONS=y The same goes for Bionic Beaver. ** Affects: linux-kvm (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/1915688 Title: Please enable CONFIG_FANOTIFY_ACCESS_PERMISSIONS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1915688/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908921] Re: No system tray detected by hp-systray
Same as above... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908921 Title: No system tray detected by hp-systray To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1908921/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908834] [NEW] do-release-upgrade not work
Public bug reported: Es konnte nicht ermittelt werden, welche Systemaktualisierungen verfügbar sind Ein unlösbares Problem trat während der Berechnung der Systemaktualisierung auf. Die wurde wahrscheinlich verursacht durch: * Inoffizielle Software-Pakete, die nicht von Ubuntu bereitgestellt werden Bitte verwenden Sie das Tool »ppa-purge« aus dem ppa-purge- Paket, um Software von einem Launchpad PPA zu entfernen und versuchen Sie die Systemaktualisierung erneut. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.41 ProcVersionSignature: Ubuntu 4.15.0-128.131-generic 4.15.18 Uname: Linux 4.15.0-128-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.21 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun Dec 20 20:31:35 2020 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to bionic on 2020-12-20 (0 days ago) ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic dist-upgrade -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908834 Title: do-release-upgrade not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1908834/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907882] [NEW] paprefs does not find modules
Public bug reported:
on ubuntu 20.10 paprefs does not find modules, as it uses a hardcoded path.
workaround:
cd /usr/lib
sudo ln -s pulse-13.99.2 pulse-13.99
see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=531251
strace paprefs 2>&1 |grep /lib/pulse
access("/usr/lib/pulse-13.99/modules/module-esound-protocol-tcp.so", F_OK) = -1
ENOENT (No such file or directory)
access("/usr/lib/pulse-13.99/modules/module-native-protocol-tcp.so", F_OK) = -1
ENOENT (No such file or directory)
access("/usr/lib/pulse-13.99/modules/module-zeroconf-publish.so", F_OK) = -1
ENOENT (No such file or directory)
access("/usr/lib/pulse-13.99/modules/module-zeroconf-discover.so", F_OK) = -1
ENOENT (No such file or directory)
access("/usr/lib/pulse-13.99/modules/module-raop-discover.so", F_OK) = -1
ENOENT (No such file or directory)
access("/usr/lib/pulse-13.99/modules/module-rtp-recv.so", F_OK) = -1 ENOENT (No
such file or directory)
access("/usr/lib/pulse-13.99/modules/module-rtp-send.so", F_OK) = -1 ENOENT (No
such file or directory)
access("/usr/lib/pulse-13.99/modules/module-rygel-media-server.so", F_OK) = -1
ENOENT (No such file or directory)
** Affects: pulseaudio (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
- paprefs does not find modules, as it uses a hardcoded path.
+ on ubuntu 20.10 paprefs does not find modules, as it uses a hardcoded path.
workaround:
cd /usr/lib
sudo ln -s pulse-13.99.2 pulse-13.99
see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=531251
strace paprefs 2>&1 |grep /lib/pulse
access("/usr/lib/pulse-13.99/modules/module-esound-protocol-tcp.so", F_OK) =
-1 ENOENT (No such file or directory)
access("/usr/lib/pulse-13.99/modules/module-native-protocol-tcp.so", F_OK) =
-1 ENOENT (No such file or directory)
access("/usr/lib/pulse-13.99/modules/module-zeroconf-publish.so", F_OK) = -1
ENOENT (No such file or directory)
access("/usr/lib/pulse-13.99/modules/module-zeroconf-discover.so", F_OK) = -1
ENOENT (No such file or directory)
access("/usr/lib/pulse-13.99/modules/module-raop-discover.so", F_OK) = -1
ENOENT (No such file or directory)
access("/usr/lib/pulse-13.99/modules/module-rtp-recv.so", F_OK) = -1 ENOENT
(No such file or directory)
access("/usr/lib/pulse-13.99/modules/module-rtp-send.so", F_OK) = -1 ENOENT
(No such file or directory)
access("/usr/lib/pulse-13.99/modules/module-rygel-media-server.so", F_OK) =
-1 ENOENT (No such file or directory)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1907882
Title:
paprefs does not find modules
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1907882/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907865] [NEW] Xorg crash
Public bug reported: I can't reliably reproduce this crash, and I don't know, even approximately, what's causing it, or what I might be doing to possibly cause it. It just randomly crashes, and dumps me back to the login screen. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Dec 11 15:35:06 2020 DistUpgraded: 2020-10-07 09:25:09,468 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: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:06de] InstallationDate: Installed on 2016-12-06 (1466 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Latitude E5470 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-56-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to focal on 2020-10-07 (65 days ago) dmi.bios.date: 06/15/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.3 dmi.board.name: 0VHKV0 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.3:bd06/15/2016:svnDellInc.:pnLatitudeE5470:pvr:rvnDellInc.:rn0VHKV0:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5470 dmi.product.sku: 06DE dmi.sys.vendor: Dell Inc. modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2020-12-09T15:53:03.120486 version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 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 xserver.bootTime: Fri Aug 17 21:02:51 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1523 vendor BOE xserver.version: 2:1.18.4-0ubuntu0.7 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug crash 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/1907865 Title: Xorg crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1907865/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1862331]
the UI btw would be "certutil" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1862331 Title: [upstream] mozilla cert8.db and key3.db are denied by apparmor To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1862331/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1862331]
well, obviously the firefox profile is used because NSS wants to find its certificates for digital signing. I would also argue that it shouldn't request "w" permissions, but "r" is expected. I also suggested using ~/.pki/nssdb but... 16:41 < _rene_> is there any plan to be able to use ~/.pki/nssdb? (see https://wiki.mozilla.org/NSS_Shared_DB_And_LINUX) 16:41 < _rene_> instead of the mozilla profile? 16:42 -!- hallnknight [~hallnknig@2401:4900:3b30:951d:983d:6f8:9c88:2aef] has joined #libreoffice-dev 16:42 < _rene_> (context: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975951 and https://bugs.documentfoundation.org/show_bug.cgi?id=119811) 16:42 < IZBot> bug 119811: LibreOffice-LibreOffice normal/medium NEW LibreOffice 6.0.6 spies on my Firefox keychain when opening MS documents 16:43 < mst___> _rene_, if there's some UI for users to add their certs to that location then sure 16:44 < _rene_> one can do so without a UI? not everything needs a UI? 16:44 < _rene_> at least make it honour that path in addition 16:45 < _rene_> mst___: users nowadays also don't use firefox :) 16:48 <@thorsten> _rene_: thought nss can only use one path? 16:49 < _rene_> no idea, can't one initialize nss two times and use one instance for firefox and the other for that one? 16:49 < _rene_> I mean, there must be more application not relying only on firefox? 16:50 <@thorsten> we had similar issues with thunderbird vs. firefox cert stores, 16:50 < _rene_> mmh 16:50 <@thorsten> IIRC the suggestion was for users to set the proper env var, 16:50 <@thorsten> and we're off the hook? 16:50 <@vmiklos> or just set their preferred path in LO, using tools -> options 16:51 < _rene_> but MOZILLA_CERTIFICATE_FOLDER if you mean that will expect a firefox profile and not work with ~/.pki/nssdb, will it? 16:52 <@vmiklos> you would have to check, possibly both just contain files like certX.db and keyY.db, so perhaps works out of the box 16:52 -!- OlegShtch [~Thunderbi@37.112.63.140] has joined #libreoffice-dev 16:52 < _rene_> ah, right, there's the "Options", didn't know 16:54 < _rene_> ok, related to this: 16:54 < _rene_> why does LO request w permissions? 16:54 < _rene_> r should simply suffice, shouldn't it? 16:55 < _rene_> or is this nss actually opening it? (I guess so...) 16:56 -!- hallnknight [~hallnknig@2401:4900:3b30:951d:983d:6f8:9c88:2aef] has quit [Ping timeout: 264 seconds] 16:56 -!- sberg [~sb...@dynamic-077-003-206-224.77.3.pool.telefonica.de] has quit [Quit: Leaving] 16:56 <@vmiklos> i guess ideally it should be read-only, right. 16:56 -!- hallnknight [~hallnknig@223.187.154.213] has joined #libreoffice-dev 16:57 * _rene_ writes that into https://bugs.documentfoundation.org/show_bug.cgi?id=119811 16:57 < IZBot> bug 119811: LibreOffice-LibreOffice normal/medium NEW LibreOffice 6.0.6 spies on my Firefox keychain when opening MS documents 16:57 < _rene_> (with the chat here cut'n'pasted) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1862331 Title: [upstream] mozilla cert8.db and key3.db are denied by apparmor To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1862331/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901363] [NEW] Updating to 1.2.4-1 breaks pulseaudio on AMD Renoir devices
Public bug reported: same issue on groovy on my Lenovo T14 AMD. https://bugs.archlinux.org/task/68313 already fixed upstream https://github.com/alsa-project/alsa-ucm-conf/issues/55 ** Affects: alsa-ucm-conf (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/1901363 Title: Updating to 1.2.4-1 breaks pulseaudio on AMD Renoir devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1901363/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872941] Re: [Ubuntu 20.04] virt-install fails to detect path after images folder name has changed
FYI: It seems that the issue is still present in the currently available focal/universe packages: virt-manager 1:2.2.1-3ubuntu2 If you run into this issue, like I did, the upstream version like Christian Ehrhardt mentioned above is needed. See also: https://github.com/virt-manager/virt-manager/issues/171 ** Bug watch added: github.com/virt-manager/virt-manager/issues #171 https://github.com/virt-manager/virt-manager/issues/171 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872941 Title: [Ubuntu 20.04] virt-install fails to detect path after images folder name has changed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1872941/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894737] [NEW] gtkglarea not working on software renderers
Public bug reported: to reproduce: install gtk-3-examples on a system with software rendering, like virtualbox. run gtk3-demo --run=glarea observe black boxes. I fixed it upstream with this commit: https://gitlab.gnome.org/GNOME/gtk/-/commit/69334021a22a79f5fddb30f0872fcf3fc6bc1cf0 ** Affects: gtk+3.0 (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/1894737 Title: gtkglarea not working on software renderers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1894737/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1859509] Re: wsl-integration.sh shows error when .cache/ can't be created
It is hard to feel any enthusiasm from Ubuntu to backport the fix. Considering how many issues I have run into trying to use Ubuntu WSL image, I am not sure Ubuntu has any real interest in WSL. Just like Apple is not really into that boot camp thingy. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1859509 Title: wsl-integration.sh shows error when .cache/ can't be created To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1859509/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874464] Re: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out
I tried the mainline kernel and the error is gone. What next? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874464 Title: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874464/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874464] Re: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out
here comes the error: [ 60.259403] [ cut here ] [ 60.259405] NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out [ 60.259416] WARNING: CPU: 6 PID: 0 at net/sched/sch_generic.c:447 dev_watchdog+0x258/0x260 [ 60.259417] Modules linked in: vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) nf_tables nfnetlink ip6table_filter ip6_tables iptable_filter bpfilter aufs overlay nls_iso8859_1 snd_hda_codec_hdmi intel_rapl_msr mei_hdcp snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_intel snd_intel_dspcfg snd_hda_codec snd_hda_core snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi intel_rapl_common bridge x86_pkg_temp_thermal intel_powerclamp stp snd_seq llc coretemp kvm_intel snd_seq_device kvm input_leds snd_timer intel_cstate intel_rapl_perf eeepc_wmi asus_wmi sparse_keymap wmi_bmof snd soundcore mei_me mei mac_hid acpi_pad sch_fq_codel parport_pc ppdev lp parport nfsd auth_rpcgss nfs_acl lockd grace sunrpc ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic usbhid hid uas usb_storage crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel [ 60.259438] crypto_simd i915 mxm_wmi i2c_algo_bit cryptd glue_helper drm_kms_helper nvme syscopyarea sysfillrect sysimgblt fb_sys_fops r8169 i2c_i801 drm nvme_core ahci realtek libahci wmi video [ 60.259444] CPU: 6 PID: 0 Comm: swapper/6 Tainted: G OE 5.4.0-33-generic #37-Ubuntu [ 60.259445] Hardware name: bluechip Computer AG BUSINESSline/Z170-K, BIOS 3805 05/16/2018 [ 60.259446] RIP: 0010:dev_watchdog+0x258/0x260 [ 60.259447] Code: 85 c0 75 e5 eb 9f 4c 89 ff c6 05 ef f6 e7 00 01 e8 6d bb fa ff 44 89 e9 4c 89 fe 48 c7 c7 40 73 e3 8f 48 89 c2 e8 03 30 71 ff <0f> 0b eb 80 0f 1f 40 00 0f 1f 44 00 00 55 48 89 e5 41 57 49 89 d7 [ 60.259448] RSP: 0018:af7200234e30 EFLAGS: 00010286 [ 60.259448] RAX: RBX: 9c6ded99fa00 RCX: 0006 [ 60.259449] RDX: 0007 RSI: 0096 RDI: 9c6df6b978c0 [ 60.259449] RBP: af7200234e60 R08: 04a0 R09: 0004 [ 60.259450] R10: R11: 0001 R12: 0001 [ 60.259450] R13: R14: 9c6defed4480 R15: 9c6defed4000 [ 60.259451] FS: () GS:9c6df6b8() knlGS: [ 60.259451] CS: 0010 DS: ES: CR0: 80050033 [ 60.259452] CR2: 1a62928112d0 CR3: 0009e1e0a002 CR4: 003606e0 [ 60.259452] DR0: DR1: DR2: [ 60.259453] DR3: DR6: fffe0ff0 DR7: 0400 [ 60.259453] Call Trace: [ 60.259454] [ 60.259456] ? pfifo_fast_enqueue+0x150/0x150 [ 60.259458] call_timer_fn+0x32/0x130 [ 60.259459] __run_timers.part.0+0x180/0x280 [ 60.259461] ? timerqueue_add+0x68/0xb0 [ 60.259462] ? enqueue_hrtimer+0x3d/0x90 [ 60.259464] ? recalibrate_cpu_khz+0x10/0x10 [ 60.259465] ? ktime_get+0x3e/0xa0 [ 60.259466] run_timer_softirq+0x2a/0x50 [ 60.259467] __do_softirq+0xe1/0x2d6 [ 60.259468] ? hrtimer_interrupt+0x13b/0x220 [ 60.259469] irq_exit+0xae/0xb0 [ 60.259470] smp_apic_timer_interrupt+0x7b/0x140 [ 60.259472] apic_timer_interrupt+0xf/0x20 [ 60.259472] [ 60.259473] RIP: 0010:cpuidle_enter_state+0xc5/0x450 [ 60.259474] Code: ff e8 9f 04 81 ff 80 7d c7 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 65 03 00 00 31 ff e8 f2 74 87 ff fb 66 0f 1f 44 00 00 <45> 85 ed 0f 88 8f 02 00 00 49 63 cd 4c 8b 7d d0 4c 2b 7d c8 48 8d [ 60.259475] RSP: 0018:af72000efe38 EFLAGS: 0246 ORIG_RAX: ff13 [ 60.259475] RAX: 9c6df6baad00 RBX: 90159dc0 RCX: 001f [ 60.259476] RDX: RSI: 1fef9fcd RDI: [ 60.259476] RBP: af72000efe78 R08: 000e07bd779e R09: 0335 [ 60.259477] R10: 9c6df6ba9a00 R11: 9c6df6ba99e0 R12: 9c6df6bb5700 [ 60.259477] R13: 0002 R14: 0002 R15: 9c6df6bb5700 [ 60.259478] ? cpuidle_enter_state+0xa1/0x450 [ 60.259479] cpuidle_enter+0x2e/0x40 [ 60.259480] call_cpuidle+0x23/0x40 [ 60.259481] do_idle+0x1dd/0x270 [ 60.259482] cpu_startup_entry+0x20/0x30 [ 60.259483] start_secondary+0x167/0x1c0 [ 60.259485] secondary_startup_64+0xa4/0xb0 [ 60.259486] ---[ end trace acbef11636a70d66 ]--- -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874464 Title: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874464/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-b
[Bug 1874464] Re: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out
I can confirm this error on my system after upgrade from bionic to focal. System works "normaly" but error appears in the logs. Adding "pcie_aspm=off" does not help in my case. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874464 Title: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874464/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1859509] Re: wsl-integration.sh shows error when .cache/ can't be created
What is the expected latency for it to reach Bionic? 1.5 months has passed since... I think there is no real benefit if it gets released in 2023 :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1859509 Title: wsl-integration.sh shows error when .cache/ can't be created To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1859509/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878384] [NEW] Error when using btrfs sub snapshot & send | receive
Public bug reported: I am creating snapshots of my /-subvolume and use send | receive for incremental transferring. Sometimes I get errors like "ERROR: cannot open /media/Backup/OS/snapshots/snap_2020-05-13_11:39/o13170-19818-0: No such file or directory" When I look deeper with the -v option, it seems like btrfs is creating a folder or something, moves it and then tries to rename the original folder. The error occures on different devices, but only when I make snapshots of the root of my os subvolume. The error occures only from time to time (perhaps every 5th to 15th snapshot) the only solution to send a new snapshot complete and then send incremental snapshots. I tried different kernels: Currently I am using 5.3.0-51-generic on one device and also tried 5.5 and 5.6. I found this topic on github, where some people have the same errors. (but I am using an own script, not that program) https://github.com/digint/btrbk/issues/223 Description:Ubuntu 19.10 Release:19.10 ** Affects: btrfs-progs (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/1878384 Title: Error when using btrfs sub snapshot & send | receive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/btrfs-progs/+bug/1878384/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878091] [NEW] Non-fractional scaling not working
Public bug reported: My laptop has a 4K display. Default Resolution = 3840x2160, scale = 200%. If I set resolution to 1920x1080, everything on the desktop is scaled to double size. So, if I reduce the Scale setting from 200% to 100%, I would expect everything to look normal again, but it does not. 100% and 200% look identical. However, if I enable Fractional scaling and select 125%, that looks correct. So, Fractional scaling works correctly, but non-fractional scaling does not. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-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.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 11 15:58:43 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller [17aa:3978] Subsystem: Lenovo GM107M [GeForce GTX 960M] [17aa:3978] InstallationDate: Installed on 2020-05-07 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20349 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=4f7e434e-f524-450c-8486-29302f1ca495 ro persistent quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.asset.tag: K0J40709WIN dmi.board.name: Lenovo Y50-70 Touch dmi.board.vendor: LENOVO dmi.board.version: K0J40709WIN dmi.chassis.asset.tag: K0J40709WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 Touch dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20349:pvrLenovoY50-70Touch:rvnLENOVO:rnLenovoY50-70Touch:rvrK0J40709WIN:cvnLENOVO:ct10:cvrLenovoY50-70Touch: dmi.product.family: IDEAPAD dmi.product.name: 20349 dmi.product.sku: LENOVO_MT_20349_BU_idea_FM_Lenovo Y50-70 Touch dmi.product.version: Lenovo Y50-70 Touch dmi.sys.vendor: LENOVO 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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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 ** Summary changed: - Non-ractional scaling not working + Non-fractional scaling not working -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878091 Title: Non-fractional scaling not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1878091/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776616] Re: Ubuntu 18.04 getting stuck at "Starting Reboot" and "Starting Power-Off"
Re #42; pardon; machine-confusion. The problem with 4.15.0-72 indeed but on a Xeon E5606, AMD HD 5770 graphics -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776616 Title: Ubuntu 18.04 getting stuck at "Starting Reboot" and "Starting Power- Off" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776616/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776616] Re: Ubuntu 18.04 getting stuck at "Starting Reboot" and "Starting Power-Off"
Re #41, "Can anyone else confirm?" For me and for a few other reports out there, the problem *started* with 4.15.0-72. Core 2 Duo with old G45 onboard graphics. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776616 Title: Ubuntu 18.04 getting stuck at "Starting Reboot" and "Starting Power- Off" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776616/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839317] Re: Grub fails to chainload the Windows Boot Manager
I'm also facing the same problem and I found a solution which worked for me on amd64. My system is using UEFI without secure boot from a gpt partitioned drive. Please try to install the package shim-signed. This fixed the problem for me. Chainloading Windows even works after uninstalling the package again. So I expect it is something related to the installation process of the package. Maybe it leaves some important files in /boot after uninstalling. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839317 Title: Grub fails to chainload the Windows Boot Manager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1839317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847883] [NEW] Startscript not passing command line arguments
Public bug reported: The startscript /usr/games/glhack is not passing the command line arguments to the executable. The script currently reads: #!/bin/sh exec /usr/lib/games/glhack/glhack but it should be: #!/bin/sh exec /usr/lib/games/glhack/glhack "$@" Then all those command line options so highly promised in the man page actually work ;-) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: glhack 1.2-4 [modified: usr/games/glhack var/games/glhack/logfile var/games/glhack/record] ProcVersionSignature: Ubuntu 5.0.0-31.33~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-31-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Oct 13 00:07:59 2019 InstallationDate: Installed on 2019-08-13 (60 days ago) InstallationMedia: Xubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: glhack UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: glhack (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847883 Title: Startscript not passing command line arguments To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glhack/+bug/1847883/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847883] Re: Startscript not passing command line arguments
The game, by default (without command line options), starts fullscreen in 800x600. This turns off my left and right monitor and makes my central monitor complain about the rather outdated resolution. The ability to pass the "--windowed" command line option this program didn't work very well on my computer. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847883 Title: Startscript not passing command line arguments To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glhack/+bug/1847883/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822048] Re: cluster report not displayed
I have the same issue and the upstream patch fixes it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822048 Title: cluster report not displayed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ganglia-web/+bug/1822048/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1737187] Re: Unable to launch AWS M5 instance with newest Ubuntu AMI
Is this still considered an issue? I booted ami-0bc11fa490cf2ead7 (ubuntu/images/hvm-ssd/ubuntu- xenial-16.04-amd64-server-20190204.3) on an m5.large in eu-west-1 and it was fine. ** Attachment added: "kern.log" https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1737187/+attachment/5236916/+files/kern.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1737187 Title: Unable to launch AWS M5 instance with newest Ubuntu AMI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1737187/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814579] [NEW] Xorg crash
Public bug reported: I'm pretty sure this might be related to bug #1769397. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Feb 4 12:34:47 2019 DistUpgraded: 2018-08-20 07:33:39,527 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:06de] InstallationDate: Installed on 2016-12-06 (790 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Latitude E5470 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to bionic on 2018-08-20 (168 days ago) dmi.bios.date: 06/15/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.3 dmi.board.name: 0VHKV0 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.3:bd06/15/2016:svnDellInc.:pnLatitudeE5470:pvr:rvnDellInc.:rn0VHKV0:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5470 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Fri Aug 17 21:02:51 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1523 vendor BOE xserver.version: 2:1.18.4-0ubuntu0.7 ** Affects: easystroke (Ubuntu) Importance: Undecided Status: New ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic crash ubuntu ** Also affects: easystroke (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/1814579 Title: Xorg crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/easystroke/+bug/1814579/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1812101]
Better late than never... > 2) The idea of gtk3_kde5 is to use the stable gtk3 VCL plugin and just add a > native KDE filepicker on top. Since LXQt cannot use that one anyway, there > seems to be little value in using gtk3_kde5 over gtk3 anyway... > I'd rather suggest to change the order, so that LXQt prefers the plain gtk3 > VCL > plugin over the gtk3_kde5 one. > > Any other opinions on this? I disagree. It's Lx*Qt*, so one should prefer the qt5 plugin. But does it have a file picker? Regards, Rene -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1812101 Title: libreoffice-kde5 file dialog/picker doesn't add extension automatically To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1812101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814069] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1814069/+attachment/5234593/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814069 Title: kernel linux-image-4.15.0-44 not booting on Hyperv Server 2008R2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814069/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814069] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1814069/+attachment/5234588/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814069 Title: kernel linux-image-4.15.0-44 not booting on Hyperv Server 2008R2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814069/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814069] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1814069/+attachment/5234594/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814069 Title: kernel linux-image-4.15.0-44 not booting on Hyperv Server 2008R2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814069/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814069] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1814069/+attachment/5234595/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814069 Title: kernel linux-image-4.15.0-44 not booting on Hyperv Server 2008R2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814069/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814069] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1814069/+attachment/5234592/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814069 Title: kernel linux-image-4.15.0-44 not booting on Hyperv Server 2008R2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814069/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814069] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1814069/+attachment/5234589/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814069 Title: kernel linux-image-4.15.0-44 not booting on Hyperv Server 2008R2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814069/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814069] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1814069/+attachment/5234591/+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/1814069 Title: kernel linux-image-4.15.0-44 not booting on Hyperv Server 2008R2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814069/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814069] Re: kernel linux-image-4.15.0-44 not booting on Hyperv Server 2008R2
apport information ** Tags added: apport-collected uec-images ** Description changed: Ubuntu stuck on booting on HyperV Server 2008R2. I saw kernel messages, seems to load ram image the boot is stuck. Seems to be a problem with hyperv drivers propably harddrive. Reverted back to the previous kernel. Description:Ubuntu 18.04.1 LTS Release:18.04Description:Ubuntu 18.04.1 LTS Release:18.04 + --- + ProblemType: Bug + AlsaDevices: + total 0 + crw-rw 1 root audio 116, 1 Jan 31 08:52 seq + crw-rw 1 root audio 116, 33 Jan 31 08:52 timer + AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' + ApportVersion: 2.20.9-0ubuntu7.5 + Architecture: amd64 + ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + DistroRelease: Ubuntu 18.04 + IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' + Lsusb: Error: command ['lsusb'] failed with exit code 1: + MachineType: Microsoft Corporation Virtual Machine + Package: linux (not installed) + PciMultimedia: + + ProcEnviron: + TERM=xterm + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 hyperv_fb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=86036ccb-bc11-11e8-93c9-00155dfd7535 ro maybe-ubiquity + ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 + RelatedPackageVersions: + linux-restricted-modules-4.15.0-43-generic N/A + linux-backports-modules-4.15.0-43-generic N/A + linux-firmware 1.173.3 + RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' + Tags: bionic uec-images + Uname: Linux 4.15.0-43-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + _MarkForUpload: True + dmi.bios.date: 03/19/2009 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: 090004 + dmi.board.name: Virtual Machine + dmi.board.vendor: Microsoft Corporation + dmi.board.version: 7.0 + dmi.chassis.asset.tag: 8531-7125-9206-2460-7819-2663-90 + dmi.chassis.type: 3 + dmi.chassis.vendor: Microsoft Corporation + dmi.chassis.version: 7.0 + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr090004:bd03/19/2009:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0: + dmi.product.name: Virtual Machine + dmi.product.version: 7.0 + dmi.sys.vendor: Microsoft Corporation ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1814069/+attachment/5234587/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814069 Title: kernel linux-image-4.15.0-44 not booting on Hyperv Server 2008R2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814069/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814069] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1814069/+attachment/5234590/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814069 Title: kernel linux-image-4.15.0-44 not booting on Hyperv Server 2008R2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814069/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814069] Re: kernel linux-image-4.15.0-44 not booting on Hyperv Server 2008R2
Kernel Version linux-image-4.15.0-44 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814069 Title: kernel linux-image-4.15.0-44 not booting on Hyperv Server 2008R2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814069/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814069] [NEW] kernel linux-image-4.15.0-44 not booting on Hyperv Server 2008R2
Public bug reported: Ubuntu stuck on booting on HyperV Server 2008R2. I saw kernel messages, seems to load ram image the boot is stuck. Seems to be a problem with hyperv drivers propably harddrive. Reverted back to the previous kernel. Description:Ubuntu 18.04.1 LTS Release:18.04Description:Ubuntu 18.04.1 LTS Release:18.04 ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814069 Title: kernel linux-image-4.15.0-44 not booting on Hyperv Server 2008R2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814069/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1812557] [NEW] Missing dependency on Ruby 2.3
Public bug reported: System info: Description:Ubuntu 18.10 Release:18.10 bro: Installed: 2.5.4-1build1 Candidate: 2.5.4-1build1 Version table: *** 2.5.4-1build1 500 500 http://us.archive.ubuntu.com/ubuntu cosmic/universe amd64 Packages 100 /var/lib/dpkg/status On trying to run bro, all I get is: $ bro lsof Failed to execute process '/usr/local/bin/bro'. Reason: The file '/usr/local/bin/bro' specified the interpreter '/usr/bin/ruby2.3', which is not an executable command. Expected: # List all web processes lsof -i :80 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: bro 2.5.4-1build1 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: KDE Date: Sun Jan 20 05:15:15 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2014-03-15 (1772 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: bro UpgradeStatus: Upgraded to cosmic on 2018-11-17 (63 days ago) ** Affects: bro (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1812557 Title: Missing dependency on Ruby 2.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bro/+bug/1812557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1789097] Re: winbind does not work after reboot on Mint 19 / Ubuntu 18.04
So glad I took the time to report this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1789097 Title: winbind does not work after reboot on Mint 19 / Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/samba/+bug/1789097/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1804603] Re: systemd-tmpfiles-setup.service fails on btrfs
Hi Brian, thank you for providing this fix. It works fine on a minimal 18.10 server. I installed systemd 239-7ubuntu10.5 on a updated system. ** Tags removed: verification-needed-cosmic ** Tags added: verification-done-cosmic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1804603 Title: systemd-tmpfiles-setup.service fails on btrfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1804603/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1804603] Re: systemd-tmpfiles-setup.service fails on btrfs
I just checked 18.10 with systemd 239-7ubuntu10.4 and it fails with the same error message. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1804603 Title: systemd-tmpfiles-setup.service fails on btrfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1804603/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1804603] Re: systemd-tmpfiles-setup.service fails on btrfs
** Attachment added: "apt log with 'Bad file descriptor' error" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1804603/+attachment/5218416/+files/term.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1804603 Title: systemd-tmpfiles-setup.service fails on btrfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1804603/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1804603] Re: systemd-tmpfiles-setup.service fails
I did some tests. This issue is clearly related to btrfs, because I can not reproduce this with ext4. If you have a different filesystem, you have a different issue, maybe the one in https://launchpad.net/bugs/1804847. How to reproduce this: 1) clean install from 'ubuntu-18.04.1-live-server-amd64.iso', all settings default but change root filesystem to btrfs. 2) system starts fine after reboot 3) issue 'apt install systemd' and get the 'Bad file descriptor' error allready during installation (attached log) 4) reboot with failing systemd-tmpfiles-setup.service I will also attach a log of the errors during apt install. ** Summary changed: - systemd-tmpfiles-setup.service fails + systemd-tmpfiles-setup.service fails on btrfs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1804603 Title: systemd-tmpfiles-setup.service fails on btrfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1804603/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1804603] Re: systemd-tmpfiles-setup.service fails
Yes but only because they have reverted the changes from CVE-2018-6954. This will come back very soon. Have a look at https://launchpad.net/ubuntu/+source/systemd/229-4ubuntu21.10 and https://launchpad.net/bugs/1804847 . ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-6954 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1804603 Title: systemd-tmpfiles-setup.service fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1804603/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1804847] Re: systemd=229-4ubuntu21.8 use of fchownat failes on some systems (openvz)
Could someone please have a look at https://launchpad.net/bugs/1804603 because the changes made to fix CVE-2018-6954 break systemd-tmpfiles also in a different way. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1804847 Title: systemd=229-4ubuntu21.8 use of fchownat failes on some systems (openvz) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1804847/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1804611] [NEW] systemd-networkd is stuck in 'configuring' with DHCP and no default route
Public bug reported: In our network setup systemd-networkd fails to configure everything correctly. Our systems have two NIC which are configured via DHCP. One NIC is in a service network without a default route. With this setup we get systemd-networkd-wait-online.service failing after timeout and the service NIC stuck in 'configuring'. Besides that, everything is working as expected. Our config: # lsb_release -rd Description:Ubuntu 18.04.1 LTS Release:18.04 # apt-cache policy systemd systemd: Installiert: 237-3ubuntu10.9 Installationskandidat: 237-3ubuntu10.9 Versionstabelle: *** 237-3ubuntu10.9 500 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Package # cat /etc/systemd/network/ens160.network [Match] Name=ens160 [Network] DHCP=ipv4 [DHCP] UseMTU=true RouteMetric=100 ClientIdentifier=mac # cat /etc/systemd/network/ens192.network [Match] Name=ens192 [Network] DHCP=ipv4 [DHCP] UseMTU=true RouteMetric=100 ClientIdentifier=mac UseRoutes=false UseDNS=false networkctl status -a ● 1: lo Link File: n/a Network File: n/a Type: loopback State: carrier (unmanaged) Address: 127.0.0.1 ::1 ● 2: ens160 Link File: n/a Network File: /etc/systemd/network/ens160.network Type: ether State: routable (configured) Path: pci-:03:00.0 Vendor: VMware Model: VMXNET3 Ethernet Controller HW Address: 00:50:56:a4:98:4c (VMware, Inc.) Address: 10.22.0.30 fe80::250:56ff:fea4:984c Gateway: 10.22.200.254 (Hewlett Packard Enterprise) DNS: 10.22.0.2 Search Domains: xxx ● 3: ens192 Link File: n/a Network File: /etc/systemd/network/ens192.network Type: ether State: routable (configuring) Path: pci-:0b:00.0 Vendor: VMware Model: VMXNET3 Ethernet Controller HW Address: 00:50:56:a4:c0:42 (VMware, Inc.) Address: 10.23.0.30 fe80::250:56ff:fea4:c042 Search Domains: This also happens in other configurations, which are more complex as soon as I add the service NIC which has no default route. systemd 239 from ubuntu 16.10 works fine. ** Affects: systemd (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/1804611 Title: systemd-networkd is stuck in 'configuring' with DHCP and no default route To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1804611/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1804603] [NEW] systemd-tmpfiles-setup.service fails on btrfs
Public bug reported: After update to systemd 237-3ubuntu10.9 systemd-tmpfiles-setup.service fails with: Nov 21 13:44:12 node-blc49 systemd[1]: Starting Create Volatile Files and Directories... Nov 21 13:44:12 node-blc49 systemd-tmpfiles[1226]: Failed to create directory or subvolume "/var": Bad file descriptor Nov 21 13:44:12 node-blc49 systemd-tmpfiles[1226]: Failed to create directory or subvolume "/home": Bad file descriptor Nov 21 13:44:12 node-blc49 systemd-tmpfiles[1226]: Failed to create directory or subvolume "/srv": Bad file descriptor Nov 21 13:44:12 node-blc49 systemd[1]: systemd-tmpfiles-setup.service: Main process exited, code=exited, status=1/FAILURE Nov 21 13:44:12 node-blc49 systemd[1]: systemd-tmpfiles-setup.service: Failed with result 'exit-code'. Nov 21 13:44:12 node-blc49 systemd[1]: Failed to start Create Volatile Files and Directories. This happens on btrfs root filesystems in real hardware and on our virtualized servers as well. 237-3ubuntu10.6 didnt show this errors and going back to 237-3ubuntu10 removes them as well. # lsb_release -rd Description:Ubuntu 18.04.1 LTS Release:18.04 # apt-cache policy systemd systemd: Installiert: 237-3ubuntu10.9 Installationskandidat: 237-3ubuntu10.9 Versionstabelle: *** 237-3ubuntu10.9 500 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ** Affects: systemd (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/1804603 Title: systemd-tmpfiles-setup.service fails on btrfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1804603/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1685442]
My vintage MacBook4,1 is obviously also affected by this: [0.00] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:41:pipe B] flip_done timed out [0.00] [ cut here ] [0.00] vblank wait timed out on crtc 1 [0.00] WARNING: CPU: 0 PID: 1158 at drivers/gpu/drm/drm_vblank.c:1084 drm_wait_one_vblank+0x15c/0x170 [drm] [0.00] Modules linked in: ipv6 kvm_intel kvm irqbypass btusb btintel btbcm btrtl bluetooth ecdh_generic b43 mac80211 deflate efi_pstore mcryptd sha256_ssse3 joydev i915 snd_hda_codec_realtek sha256_generic snd_hda_codec_generic gpio_ich snd_hda_intel snd_hda_codec snd_hda_core applesmc input_leds drm_kms_helper hwmon appletouch isight_firmware snd_hwdep input_polldev cfg80211 drm fb_sys_fops sysimgblt sysfillrect rfkill syscopyarea snd_pcm i2c_algo_bit bcma snd_timer i2c_i801 rng_core snd pcspkr i2c_core intel_agp led_class ssb_hcd lpc_ich intel_gtt soundcore efivars apple_bl acpi_cpufreq dm_crypt ecb glue_helper crypto_simd cryptd aes_x86_64 xts algif_skcipher af_alg hid_apple dm_mod xfs udf reiserfs ntfs jfs isofs vfat msdos fat ext4 jbd2 crc16 ext2 mbcache dlm fscrypto configfs btrfs raid6_pq [0.00] zstd_compress xor libcrc32c raid1 md_mod sr_mod ide_gd_mod hid_appleir hid_generic usbhid hid uas usb_storage ide_generic firewire_sbp2 sg sd_mod ide_cd_mod cdrom pata_acpi ide_pci_generic ata_generic ata_piix ahci libahci ehci_pci ehci_hcd uhci_hcd firewire_ohci firewire_core crc_itu_t piix ssb sky2 libata usbcore usb_common [0.00] CPU: 0 PID: 1158 Comm: X Tainted: GW 4.17.6-dist #1 [0.00] Hardware name: Apple Inc. MacBook4,1/Mac-F22788A9, BIOS MB41.88Z.00C1.B00.0802091535 02/09/08 [0.00] RIP: 0010:drm_wait_one_vblank+0x15c/0x170 [drm] [0.00] RSP: 0018:a36d402f7a08 EFLAGS: 00010286 [0.00] RAX: RBX: 95732e4b RCX: 0006 [0.00] RDX: 0007 RSI: 0096 RDI: 95733fc15390 [0.00] RBP: 0001 R08: 0030 R09: 0512 [0.00] R10: R11: 0001 R12: [0.00] R13: 0b09 R14: 95732e661968 R15: 9573297fa800 [0.00] FS: 7f84795bbcc0() GS:95733fc0() knlGS: [0.00] CS: 0010 DS: ES: CR0: 80050033 [0.00] CR2: 01684038 CR3: 00012b90a000 CR4: 06f0 [0.00] Call Trace: [0.00] ? wait_woken+0x80/0x80 [0.00] intel_get_load_detect_pipe+0x365/0x3b0 [i915] [0.00] intel_tv_detect+0x126/0x490 [i915] [0.00] ? merge+0x59/0xb0 [0.00] ? drm_modeset_lock+0x2b/0xa0 [drm] [0.00] drm_helper_probe_single_connector_modes+0xce/0x6b0 [drm_kms_helper] [0.00] drm_mode_getconnector+0x2c3/0x2f0 [drm] [0.00] ? _cond_resched+0x10/0x20 [0.00] ? mutex_lock+0x9/0x30 [0.00] ? drm_mode_connector_property_set_ioctl+0x50/0x50 [drm] [0.00] drm_ioctl_kernel+0x56/0xb0 [drm] [0.00] drm_ioctl+0x18d/0x350 [drm] [0.00] ? drm_mode_connector_property_set_ioctl+0x50/0x50 [drm] [0.00] ? __fpu__restore_sig+0x70/0x410 [0.00] do_vfs_ioctl+0x9f/0x5f0 [0.00] ? _copy_from_user+0x37/0x60 [0.00] ksys_ioctl+0x35/0x70 [0.00] __x64_sys_ioctl+0x11/0x20 [0.00] do_syscall_64+0x5a/0x170 [0.00] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [0.00] RIP: 0033:0x7f847713ebb7 [0.00] RSP: 002b:7ffc5f9fb338 EFLAGS: 3246 ORIG_RAX: 0010 [0.00] RAX: ffda RBX: 01684f80 RCX: 7f847713ebb7 [0.00] RDX: 7ffc5f9fb370 RSI: c05064a7 RDI: 000c [0.00] RBP: 000c R08: 001e14ebd77f85a3 R09: 7ffc5facb080 [0.00] R10: ed2c R11: 3246 R12: c05064a7 [0.00] R13: 7ffc5f9fb370 R14: 7ffc5f9fb370 R15: 01684e30 [0.00] Code: 5f f6 0f 0b e9 32 ff ff ff 48 89 e6 4c 89 f7 e8 cb ad 62 f6 45 85 e4 0f 85 14 ff ff ff 89 ee 48 c7 c7 38 cf a7 c0 e8 eb 26 5f f6 <0f> 0b e9 ff fe ff ff e8 28 25 5f f6 0f 1f 84 00 00 00 00 00 8b [0.00] ---[ end trace 10a5ec3e58e1a8d1 ]--- -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1685442 Title: Errors: flip_done timed out during boot-up; slow boot To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1685442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1685442]
(In reply to Ville Syrjala from comment #78) > Fixes posted: > https://patchwork.freedesktop.org/series/52378/ Awesome, big thanks! Works for me, tested on MacBook4,1 https://www.youtube.com/watch?v=GqH21-KcFzU -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1685442 Title: Errors: flip_done timed out during boot-up; slow boot To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1685442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1788997] Re: rtl8723be wifi does not work under linux-modules-extra-4.15.0-33-generic
I also tested last kernel from mainline (following #25 & #26 ,just for confirmation...) [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19 modinfo rtl8723be says: filename: /lib/modules/4.19.0-041900-generic/kernel/drivers/net/wireless/realtek/rtlwifi/rtl8723be/rtl8723be.ko firmware: rtlwifi/rtl8723befw_36.bin firmware: rtlwifi/rtl8723befw.bin srcversion: CF0CBB2F4446A615D0ABCBE similarily with comment #58 wifi works out of the box (no ant_sel) it works also fine with ant_sel=0 (supposed to be equivalent) it works also fine with ant_sel=1 does not work with ant_sel=2 like for comment #53, the working ant_sel changed compared to reference kernel 4.15.0-32 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1788997 Title: rtl8723be wifi does not work under linux-modules- extra-4.15.0-33-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788997/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1788997] Re: rtl8723be wifi does not work under linux-modules-extra-4.15.0-33-generic
I tested last proposed kernel 4.15.0-39, but the issue is still there, no signal with either no ant_sel, ant_sel=0, ant_sel=1 or ant_sel=2. In my environment the last working kernel is 4.15.0-32 with ant_sel=2. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1788997 Title: rtl8723be wifi does not work under linux-modules- extra-4.15.0-33-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788997/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1789097] Re: winbind does not work after reboot on Mint 19 / Ubuntu 18.04
Upstream seems silent; bug remains in NEW state and no follow-up. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1789097 Title: winbind does not work after reboot on Mint 19 / Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/samba/+bug/1789097/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1789097] Re: winbind does not work after reboot on Mint 19 / Ubuntu 18.04
Actually, no, that doesn't work for me. Was expecting it would given the comments on the samba bug, but, well, no. It *does* work to send HUP once booted: rene@t5500:~$ ping WD-NETCENTER ping: WD-NETCENTER: Name or service not known rene@t5500:~$ sudo kill -HUP $(systemctl show winbind -p MainPID --value) rene@t5500:~$ ping WD-NETCENTER PING WD-NETCENTER (192.168.1.33) 56(84) bytes of data. 64 bytes from fs7-netcenter (192.168.1.33): icmp_seq=1 ttl=64 time=1.86 ms It seems the networkd-dispatcher script is still too early. Must by the way also admit I'd maybe not consider it a better workaround even it if did work than just waiting for network-online.target; nmbd as mentioned already does as well, so only people with minimal Windows- networking needs or wants would get any potential benefit from NOT simply waiting for network-online.target. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1789097 Title: winbind does not work after reboot on Mint 19 / Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/samba/+bug/1789097/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1789097] Re: winbind does not work after reboot on Mint 19 / Ubuntu 18.04
As to the reply you got on https://bugzilla.samba.org/show_bug.cgi?id=13607, I can deny a "net cache flush" doing anything to get WINS name resolving going for me when booted with the original service file: rene@t5500:~$ ping WD-NETCENTER ping: WD-NETCENTER: Name or service not known rene@t5500:~$ net cache flush rene@t5500:~$ ping WD-NETCENTER ping: WD-NETCENTER: Name or service not known -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1789097 Title: winbind does not work after reboot on Mint 19 / Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/samba/+bug/1789097/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1789097] Re: winbind does not work after reboot on Mint 19 / Ubuntu 18.04
** Attachment added: "winbind.service-working" https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1789097/+attachment/5185183/+files/winbind.service-working -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1789097 Title: winbind does not work after reboot on Mint 19 / Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1789097/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1789097] Re: winbind does not work after reboot on Mint 19 / Ubuntu 18.04
Thanks much for checking. I see; I was expecting this to be an
"immediately obvious" sort of thing to someone with unlike me an actual
clue about samba/winbind, but I have with the above guidance nos
supplied more information.
Specifically, it would appear that your explicitly mentioned "wins
server" configuration will be the difference. I never expected my
/etc/samba/smb.conf to be relevant since mine is fully vanilla, as
provided by the "samba-common" package. It is also attached, but:
rene@t5500:~$ debsums samba-common | grep /usr/share/samba/smb.conf
/usr/share/samba/smb.conf OK
rene@t5500:~$ cmp /usr/share/samba/smb.conf /etc/samba/smb.conf
rene@t5500:~$
This is to say that I do not in fact have a WINS server specified; that
judging by the logs my winbind is relying on broadcasts, and bombing out
in that case if started before network-online.target.
There's two logs attached with "debug level = 5", one log.winbindd-
nonworking and one log.winbindd-working, in which "nonworking" is
without /etc/systemd/system/winbind.service (i.e., default) and working
with.
In the nonworking situation the log shows:
[2018/09/05 22:44:21.132692, 0] ../lib/util/become_daemon.c:124(daemon_ready)
STATUS=daemon 'winbindd' finished starting up and ready to serve connections
[2018/09/05 22:44:42.487584, 3]
../source3/winbindd/winbindd_misc.c:395(winbindd_interface_version)
[ 1917]: request interface version (version = 29)
[2018/09/05 22:44:42.487775, 3]
../source3/winbindd/winbindd_misc.c:428(winbindd_priv_pipe_dir)
[ 1917]: request location of privileged pipe
[2018/09/05 22:44:42.487995, 3]
../source3/winbindd/winbindd_wins_byname.c:56(winbindd_wins_byname_send)
[ 1917]: wins_byname WD-NETCENTER
[2018/09/05 22:44:42.488050, 3]
../source3/libsmb/namequery.c:2142(resolve_wins_send)
resolve_wins: WINS server resolution selected and no WINS servers listed.
[2018/09/05 22:44:42.488086, 3]
../source3/libsmb/namequery.c:1880(name_resolve_bcast_send)
name_resolve_bcast: Attempting broadcast lookup for name WD-NETCENTER<0x20>
and silence after that, whereas in the working situation:
[2018/09/05 22:39:51.454142, 0] ../lib/util/become_daemon.c:124(daemon_ready)
STATUS=daemon 'winbindd' finished starting up and ready to serve connections
[2018/09/05 22:40:41.498139, 3]
../source3/winbindd/winbindd_misc.c:395(winbindd_interface_version)
[ 1992]: request interface version (version = 29)
[2018/09/05 22:40:41.498346, 3]
../source3/winbindd/winbindd_misc.c:428(winbindd_priv_pipe_dir)
[ 1992]: request location of privileged pipe
[2018/09/05 22:40:41.498570, 3]
../source3/winbindd/winbindd_wins_byname.c:56(winbindd_wins_byname_send)
[ 1992]: wins_byname WD-NETCENTER
[2018/09/05 22:40:41.498627, 3]
../source3/libsmb/namequery.c:2142(resolve_wins_send)
resolve_wins: WINS server resolution selected and no WINS servers listed.
[2018/09/05 22:40:41.498676, 3]
../source3/libsmb/namequery.c:1880(name_resolve_bcast_send)
name_resolve_bcast: Attempting broadcast lookup for name WD-NETCENTER<0x20>
[2018/09/05 22:40:41.499722, 4]
../source3/libsmb/nmblib.c:108(debug_nmb_packet)
nmb packet from 192.168.1.33(35072) header: id=7546 opcode=Query(0)
response=Yes
header: flags: bcast=No rec_avail=Yes rec_des=Yes trunc=No auth=Yes
header: rcode=0 qdcount=0 ancount=1 nscount=0 arcount=0
answers: nmb_name=WD-NETCENTER<20> rr_type=32 rr_class=1 ttl=259200
answers 0 char .! hex C0A80121
[2018/09/05 22:40:41.499808, 2]
../source3/libsmb/namequery.c:1430(name_query_validator)
Got a positive name query response from 192.168.1.33 ( 192.168.1.33 )
The accompanying -nonworking and -working service files are also
attached but their only difference is as already described:
rene@t5500:~$ diff -u /{lib,etc}/systemd/system/winbind.service
--- /lib/systemd/system/winbind.service 2018-08-06 13:30:25.0 +0200
+++ /etc/systemd/system/winbind.service 2018-09-05 22:12:10.650061750 +0200
@@ -1,7 +1,8 @@
[Unit]
Description=Samba Winbind Daemon
Documentation=man:winbindd(8) man:samba(7) man:smb.conf(5)
-After=network.target nmbd.service
+After=network-online.target nmbd.service
+Wants=network-online.target
[Service]
Type=notify
So, I guess it's broadcasts that need network-online.target. Seeing as
how relying on those is the vanilla situation I take it this still means
the "winbind" package wants the service file adjustment?
** Attachment added: "log.winbindd-nonworking"
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1789097/+attachment/5185180/+files/log.winbindd-nonworking
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1789097
Title:
winbind does not work after reboot on Mint 19 / Ub
[Bug 1789097] Re: winbind does not work after reboot on Mint 19 / Ubuntu 18.04
** Attachment added: "log.winbindd-working" https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1789097/+attachment/5185181/+files/log.winbindd-working -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1789097 Title: winbind does not work after reboot on Mint 19 / Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1789097/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1789097] Re: winbind does not work after reboot on Mint 19 / Ubuntu 18.04
** Attachment added: "winbind.service-nonworking" https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1789097/+attachment/5185184/+files/winbind.service-nonworking -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1789097 Title: winbind does not work after reboot on Mint 19 / Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1789097/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1789097] Re: winbind does not work after reboot on Mint 19 / Ubuntu 18.04
** Attachment added: "log.winbindd-nonworking" https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1789097/+attachment/5185182/+files/log.winbindd-nonworking -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1789097 Title: winbind does not work after reboot on Mint 19 / Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1789097/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1789097] Re: winbind does not work after reboot on Mint 19 / Ubuntu 18.04
Oh, and the mentioned vanilla smb.conf... ** Attachment added: "smb.conf" https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1789097/+attachment/5185185/+files/smb.conf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1789097 Title: winbind does not work after reboot on Mint 19 / Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1789097/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1788997] Re: rtl8723be wifi does not work under linux-modules-extra-4.15.0-33-generic
Hello, I have difficulties trying your test kernel. maybe because I use signed kernel with secure boot ? In the instruction you talk about linux-image and linux-image-extra .deb packages linux-image-extra is not in folder. image is unsigned, and do not install. So I installed headers, modules, modules-extra. rtl8723be do not load anymore (because not signed). Could you confirm test procedure for 16.04 LT HWE with uefi secureboot ? Thank you in advance. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1788997 Title: rtl8723be wifi does not work under linux-modules- extra-4.15.0-33-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788997/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1789097] Re: winbind does not work after reboot on Mint 19 / Ubuntu 18.04
Just to add: the issue's the same and fully constant on an Intel Xeon E5606 @2,13GHz with 8GiB running Mint 19 Cinnamon 64-bit, and an Intel Core 2 Duo E8400 @ 3GHz withj 4GiB running Mint 19 Xfce 64-bit. That is... it's not a subtle race and I assume anyone will see this if installing only "winbind" and not the rest of "samba". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1789097 Title: winbind does not work after reboot on Mint 19 / Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1789097/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1789097] Re: winbind does not work after reboot on Mint 19 / Ubuntu 18.04
Yes, the network itself comes up fine. "Does not work" simply means that NetBIOS name resolution is unavailable even after it does; that e.g. "ping NAS" for "NAS" the NetBIOS name of my, well, NAS, tells me the name cannot be resolved. There would not appear to be relevant logs nor configuration files. The issue is simply that with "After=network.target" rather then "After =network-online.target" the winbindd daemon is started too early; does start, but does not work. Needs to be restarted for it to start to work. I am as mentioned on Linux Mint 19 but would be surprised if this were not the case on Ubuntu 18.04 itself as well. This is a standard, wired desktop without even wireless available. It is easy to reproduce: have the "winbind" and "libnss-winbind" packages installed but not "samba" itself, enable WINS name resolution in /etc/nsswitch.con as detailed and as normal, and reboot. As also mentioned, installing "samba" itself hides the issue by winbind having a dependency on nmbd and nmbd in turn on network-online.target; without "samba", we appear to have a simple systemd bootup race, solved by having it depend on network-online.target itself. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1789097 Title: winbind does not work after reboot on Mint 19 / Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1789097/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1788997] Re: rtl8723be wifi does not work under linux-modules-extra-4.15.0-33-generic
I have hp-15-ac167nf with wireless chip rtl8723be and ubuntu xenial 16.04 LTS and HWE. I got same issue: module rtl8723be option ant_sel=2 is not working anymore from kernel 4.15.0-33. As a workaround I boot previous kernel 4.15.0-32 (from grub menu). On same PC, I tried ubuntu bionic 18.04, and symptoms are exactly the same. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1788997 Title: rtl8723be wifi does not work under linux-modules- extra-4.15.0-33-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788997/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1789097] [NEW] winbind does not work after reboot on Mint 19 / Ubuntu 18.04
Public bug reported:
[copied from the Linux Mint forum]
Just installed Mint 19 and noticed a WINS name resolution buglet. I
assume this applies to Ubuntu 18.04 as well.
Windows, i.e., NetBIOS, name resolution is on Linux provided for by the
"winbindd" daemon, part of the Samba suite. One does not need either of
the other two Samba daemons "smbd" and "nmbd" when NetBIOS name
resolution is all you need: sudo apt-get install libnss-winbind (which
additionally pulls in "winbind" itself) and adding "wins" before "dns"
to the "hosts" line of /etc/nsswitch.conf is enough.
While this works fine directly after installation it does no more after
reboot due to a systemd unit file dependency issue. The standard
/lib/systemd/system/winbind.service orders itself after "network.target"
and "nmbd.service" which if you do not in fact have "samba" hence
"nmbd.service" installed amounts to "network.target" only. It however
needs "network-online.target" -- itself a dependency of "smbd.service"
if you do have that installed as well.
You can solve things by copying the unit file to its corresponding
directory under /etc and editing it,
sudo cp /{lib,etc}/systemd/system/winbind.service
xed admin:/etc/systemd/system/winbind.service
to change the line
After=network.target nmbd.service
to the two lines
After=network-online.target nmbd.service
Wants=network-online.target
After save and reboot you will have NetBIOS name resolution functional
without all of the rest of Samba running.
Note that although this fix is not needed when you do have "samba"
itself installed the above is still fine also the
** Affects: samba (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1789097
Title:
winbind does not work after reboot on Mint 19 / Ubuntu 18.04
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1789097/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787948] [NEW] environment-modules should depend on tcl and not on tcl8.6
Public bug reported: # lsb_release -rd Description:Ubuntu 18.04.1 LTS Release:18.04 # apt-cache policy environment-modules environment-modules: Installiert: 4.1.1-1 Installationskandidat: 4.1.1-1 Versionstabelle: *** 4.1.1-1 500 500 http://de.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status Installing environment-modules on a clean server install pulls in tcl8.6 as a dependency. After installation no tclsh is available, but its needed by e.g. /usr/share/modules/init/bash. Installing tcl makes /usr/bin/tclsh available. ** Affects: modules (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/1787948 Title: environment-modules should depend on tcl and not on tcl8.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modules/+bug/1787948/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1738630] Re: [improvement] xkb configuration cannot be extended without rebuilding xkb-data package
I've run into the same problem. Yes, a "plugin"-type system would solve the problem. To get in on par with other Xorg config stuff, it should be able to read system wide configurations provided by the admin, but possibly also enable user specific layouts from their home directory (so i don't have to ask for root permission to reconfigure the keyboard layout when using some elses Linux computer for a day, i can just install my config file in ~/.config/xkb/* or whatever). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1738630 Title: [improvement] xkb configuration cannot be extended without rebuilding xkb-data package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1738630/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787557] [NEW] ubuntu.com 18.04.1 + compiz + cairo-dock is getting hard to keep stable
Public bug reported: i don't know if this is allowed, but it's by far the most efficient way to report my bug to multiple development teams.. my entire computer crashed into a pulp yesterday, when i changed 1 simple setting in compiz while running cairo-dock as a window-manager/desktop environment (using the option 'ciaro-dock (Gnome)' in the ubuntu login menu, and i had to jump though a lot of hoops and call for tips, to get my system up and running again. a live blog is at https://ubuntuforums.org/showthread.php?t=2398710 - it's as concise as i could be yesterday, and once again, this could be cause by any number of components, so i'm reporting it to several development teams as a web-link to ubuntuforums.org feel free to reply right here, i'll update my thread at ubuntu forums if and when necessary with any information found on pages like these. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-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 396.51 Tue Jul 31 10:43:06 PDT 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3) .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity:Unity7:ubuntu Date: Fri Aug 17 11:25:15 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 396.51, 4.15.0-29-generic, x86_64: installed nvidia, 396.51, 4.15.0-32-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP107 [GeForce GTX 1050 Ti] [1043:85d1] GsettingsChanges: b'org.compiz.core' b'active-plugins' b"['core', 'composite', 'opengl', 'place', 'regex', 'resize', 'session', 'snap', 'vpswitch', 'wall', 'animation', 'commands', 'compiztoolbox', 'copytex', 'fade', 'grid', 'imgpng', 'mousepoll', 'move', 'obs', 'scale', 'unitymtgrabhandles', 'workarounds', 'expo', 'ezoom', 'unityshell', 'dbus', 'staticswitcher']" InstallationDate: Installed on 2018-08-17 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: System manufacturer System Product Name PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic root=UUID=950a57d8-b7de-47e9-b572-791c58a4091c ro quiet splash vt.handoff=1 SourcePackage: compiz UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/29/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3007 dmi.board.asset.tag: Default string dmi.board.name: SABERTOOTH Z170 MARK 1 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3007:bd11/29/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTHZ170MARK1:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: compiz (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic compiz-0.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/1787557 Title: ubuntu.com 18.04.1 + compiz + cairo-dock is getting hard to keep stable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1787557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787456] [NEW] Locally modified keyboard layouts overwritten on update without asking the user
Public bug reported: Locally modified keyboard layouts are overwritten on package upgrades (in my case from 16.04 to 18.04) without asking if the user wants to keep the local version or install the maintainers version. This leads to problems and extra work for the system administrator. The correct solution would be (in my opinion at least) to do the same checks for files in /usr/share/X11/xkb/* as is done for (most) config files in /etc. E.g. check the file against the currently installed package before upgrading, if it differs, ask the user what to do. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xkb-data 2.23.1-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 BootLog: CurrentDesktop: XFCE Date: Thu Aug 16 19:57:02 2018 Dependencies: DistUpgraded: 2018-08-16 14:12:51,407 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic root=UUID=4f184485-213c-4467-b6d1-3bf9fa0c69c8 ro SourcePackage: xkeyboard-config UpgradeStatus: Upgraded to bionic on 2018-08-16 (0 days ago) dmi.bios.date: 02/13/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.70 dmi.board.name: X79 Extreme4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.70:bd02/13/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX79Extreme4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xkeyboard-config (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787456 Title: Locally modified keyboard layouts overwritten on update without asking the user To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1787456/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787411] Re: doc-base post-installation script breaks do-release-upgrade from 16.04 to 18.04
Yes, i had to fiddle around quite a lot with the package manager to get everything going again and it all works now (the apport information above is from after the upgrade). That doesn't change the fact that a do-release-upgrade shouldn't just fail in the middle and give up. In my opinion, it should try to upgrade/install as much as possible and then print the couple of missing/broken packages at the end. At the very least, do-release-upgrade shouldn't just die without giving the user at least some basic information of what to try next. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787411 Title: doc-base post-installation script breaks do-release-upgrade from 16.04 to 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787411/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787411] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1787411/+attachment/5176442/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787411 Title: doc-base post-installation script breaks do-release-upgrade from 16.04 to 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787411/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787411] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1787411/+attachment/5176445/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787411 Title: doc-base post-installation script breaks do-release-upgrade from 16.04 to 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787411/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787411] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1787411/+attachment/5176441/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787411 Title: doc-base post-installation script breaks do-release-upgrade from 16.04 to 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787411/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787411] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1787411/+attachment/5176444/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787411 Title: doc-base post-installation script breaks do-release-upgrade from 16.04 to 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787411/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787411] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1787411/+attachment/5176443/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787411 Title: doc-base post-installation script breaks do-release-upgrade from 16.04 to 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787411/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787411] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1787411/+attachment/5176440/+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/1787411 Title: doc-base post-installation script breaks do-release-upgrade from 16.04 to 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787411/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787411] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1787411/+attachment/5176439/+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/1787411 Title: doc-base post-installation script breaks do-release-upgrade from 16.04 to 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787411/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787411] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1787411/+attachment/5176436/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787411 Title: doc-base post-installation script breaks do-release-upgrade from 16.04 to 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787411/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787411] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1787411/+attachment/5176438/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787411 Title: doc-base post-installation script breaks do-release-upgrade from 16.04 to 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787411/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787411] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1787411/+attachment/5176437/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787411 Title: doc-base post-installation script breaks do-release-upgrade from 16.04 to 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787411/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787411] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1787411/+attachment/5176434/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787411 Title: doc-base post-installation script breaks do-release-upgrade from 16.04 to 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787411/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787411] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1787411/+attachment/5176435/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787411 Title: doc-base post-installation script breaks do-release-upgrade from 16.04 to 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787411/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787411] AudioDevicesInUse.txt
apport information ** Attachment added: "AudioDevicesInUse.txt" https://bugs.launchpad.net/bugs/1787411/+attachment/5176432/+files/AudioDevicesInUse.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787411 Title: doc-base post-installation script breaks do-release-upgrade from 16.04 to 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787411/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787411] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1787411/+attachment/5176433/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787411 Title: doc-base post-installation script breaks do-release-upgrade from 16.04 to 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787411/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787411] Re: doc-base post-installation script breaks do-release-upgrade from 16.04 to 18.04
apport information ** Tags added: apport-collected bionic ** Description changed: On one of my computers, do-release-upgrade from 16.04 LTS to 18.04 LTS broke mid-update. Logfile seems to indicate that the "doc-base" package is to blame: 2018-08-16 14:02:43,476 INFO cache.commit() 2018-08-16 14:02:43,476 DEBUG failed to SystemUnLock() (E:Not locked) 2018-08-16 14:12:31,145 ERROR got an error from dpkg for pkg: 'doc-base': 'installed doc-base package post-installation script subprocess returned error exit status 10' 2018-08-16 14:12:31,146 DEBUG running apport_pkgfailure() doc-base: installed doc-base package post-installation script subprocess returned error exit status 10 2018-08-16 14:12:32,550 ERROR Exception during pm.DoInstall() Traceback (most recent call last): File "/tmp/ubuntu-release-upgrader-7ytclj_8/DistUpgrade/DistUpgradeView.py", line 220, in run res = pm.do_install(self.writefd) SystemError: E:Sub-process /usr/bin/dpkg returned an error code (1) 2018-08-16 14:12:32,580 ERROR SystemError from cache.commit(): installArchives() failed 2018-08-16 14:12:32,581 ERROR found exception: 'E:Sub-process /usr/bin/dpkg returned an error code (1)' 2018-08-16 14:12:51,407 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.2 + Architecture: amd64 + CurrentDesktop: XFCE + DistroRelease: Ubuntu 18.04 + HibernationDevice: RESUME=UUID=639239a3-685e-4265-abf9-da9db3964d42 + MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. + NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia + Package: linux (not installed) + ProcFB: 0 VESA VGA + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic root=UUID=4f184485-213c-4467-b6d1-3bf9fa0c69c8 ro + ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 + RelatedPackageVersions: + linux-restricted-modules-4.15.0-32-generic N/A + linux-backports-modules-4.15.0-32-generic N/A + linux-firmware 1.173.1 + RfKill: + + Tags: bionic + Uname: Linux 4.15.0-32-generic x86_64 + UpgradeStatus: Upgraded to bionic on 2018-08-16 (0 days ago) + UserGroups: adm cdrom dialout dip libvirt libvirtd lpadmin plugdev sambashare sudo vboxusers wireshark + _MarkForUpload: True + dmi.bios.date: 02/13/2014 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: P3.70 + dmi.board.name: X79 Extreme4 + dmi.board.vendor: ASRock + dmi.chassis.asset.tag: To Be Filled By O.E.M. + dmi.chassis.type: 3 + dmi.chassis.vendor: To Be Filled By O.E.M. + dmi.chassis.version: To Be Filled By O.E.M. + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.70:bd02/13/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX79Extreme4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: + dmi.product.family: To Be Filled By O.E.M. + dmi.product.name: To Be Filled By O.E.M. + dmi.product.version: To Be Filled By O.E.M. + dmi.sys.vendor: To Be Filled By O.E.M. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1787411/+attachment/5176431/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787411 Title: doc-base post-installation script breaks do-release-upgrade from 16.04 to 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787411/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787411] Re: doc-base post-installation script breaks do-release-upgrade from 16.04 to 18.04
** Attachment added: "history.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787411/+attachment/5176333/+files/history.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787411 Title: doc-base post-installation script breaks do-release-upgrade from 16.04 to 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787411/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787411] Re: doc-base post-installation script breaks do-release-upgrade from 16.04 to 18.04
** Attachment added: "screenlog.0" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787411/+attachment/5176335/+files/screenlog.0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787411 Title: doc-base post-installation script breaks do-release-upgrade from 16.04 to 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787411/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
