[Touch-packages] [Bug 2004003] [NEW] /etc/network/if-up.d/resolved: line 20: return: can only `return' from a function or sourced script
Public bug reported: Just found the following errors in "systemctl status networking" × networking.service - Raise network interfaces Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Fri 2023-01-27 12:26:29 MSK; 3min 10s ago Docs: man:interfaces(5) Process: 3963 ExecStart=/sbin/ifup -a --read-environment (code=exited, status=1/FAILURE) Main PID: 3963 (code=exited, status=1/FAILURE) CPU: 147ms янв 27 12:26:29 gerbera systemd[1]: Starting Raise network interfaces... янв 27 12:26:29 gerbera ifup[3976]: /etc/network/if-up.d/resolved: line 12: mystatedir: command not found янв 27 12:26:29 gerbera ifup[3973]: /etc/network/if-up.d/resolved: line 20: return: can only `return' from a function or sourced script янв 27 12:26:29 gerbera ifup[3969]: run-parts: /etc/network/if-up.d/resolved exited with return code 2 янв 27 12:26:29 gerbera ifup[3963]: ifup: failed to bring up lo янв 27 12:26:29 gerbera systemd[1]: networking.service: Main process exited, code=exited, status=1/FAILURE янв 27 12:26:29 gerbera systemd[1]: networking.service: Failed with result 'exit-code'. янв 27 12:26:29 gerbera systemd[1]: Failed to start Raise network interfaces. The error with mystatedir has been already reported as bug#1907878. However, patches there do not fix unexpected return statement. ** Affects: ifupdown (Ubuntu) Importance: Undecided Status: New ** Tags: jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/2004003 Title: /etc/network/if-up.d/resolved: line 20: return: can only `return' from a function or sourced script Status in ifupdown package in Ubuntu: New Bug description: Just found the following errors in "systemctl status networking" × networking.service - Raise network interfaces Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Fri 2023-01-27 12:26:29 MSK; 3min 10s ago Docs: man:interfaces(5) Process: 3963 ExecStart=/sbin/ifup -a --read-environment (code=exited, status=1/FAILURE) Main PID: 3963 (code=exited, status=1/FAILURE) CPU: 147ms янв 27 12:26:29 gerbera systemd[1]: Starting Raise network interfaces... янв 27 12:26:29 gerbera ifup[3976]: /etc/network/if-up.d/resolved: line 12: mystatedir: command not found янв 27 12:26:29 gerbera ifup[3973]: /etc/network/if-up.d/resolved: line 20: return: can only `return' from a function or sourced script янв 27 12:26:29 gerbera ifup[3969]: run-parts: /etc/network/if-up.d/resolved exited with return code 2 янв 27 12:26:29 gerbera ifup[3963]: ifup: failed to bring up lo янв 27 12:26:29 gerbera systemd[1]: networking.service: Main process exited, code=exited, status=1/FAILURE янв 27 12:26:29 gerbera systemd[1]: networking.service: Failed with result 'exit-code'. янв 27 12:26:29 gerbera systemd[1]: Failed to start Raise network interfaces. The error with mystatedir has been already reported as bug#1907878. However, patches there do not fix unexpected return statement. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/2004003/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1945853] Re: mate-screensaver crashed with SIGSEGV in matemenu_tree_item_ref()
*** This bug is a duplicate of bug 1943369 *** https://bugs.launchpad.net/bugs/1943369 Norbert, I tested an .iso image with VirtualBox and saw Apport window when I was going to turn off the virtual machine. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1945853 Title: mate-screensaver crashed with SIGSEGV in matemenu_tree_item_ref() Status in glib2.0 package in Ubuntu: Confirmed Status in mate-screensaver package in Ubuntu: Confirmed Bug description: I found this casually when I was testing the latest Ubuntu MATE 21.10 Beta. I have no idea what may cause the crash. ProblemType: Crash DistroRelease: Ubuntu 21.10 Package: mate-screensaver 1.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.465 CurrentDesktop: MATE Date: Sat Oct 2 07:53:08 2021 ExecutablePath: /usr/bin/mate-screensaver ExecutableTimestamp: 1629565330 LiveMediaBuild: Ubuntu-MATE 21.10 "Impish Indri" - Beta amd64 (20211002) ProcCmdline: mate-screensaver ProcCwd: /home/ubuntu-mate ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fc222155b07 : lock addl $0x1,(%rdi) PC (0x7fc222155b07) ok source "$0x1" ok destination "(%rdi)" (0x) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: mate-screensaver StacktraceTop: matemenu_tree_item_ref () from /lib/x86_64-linux-gnu/libmate-menu.so.2 gs_theme_manager_lookup_theme_info () ?? () ?? () g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: mate-screensaver crashed with SIGSEGV in matemenu_tree_item_ref() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1945853/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1888046] [NEW] Please merge coreutils 8.32-2 (main) from Debian unstable (main)
Public bug reported: New coreutils features are missing in Ubuntu. Especially, "ls --time=birth" available since 8.32, and time of file creation in stat(1) on btrfs or ext4 fixed since 8.31. Please consider to incorporate these features at least into Ubuntu 20.10 (Groovy Gorilla). ** Affects: coreutils (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1888046 Title: Please merge coreutils 8.32-2 (main) from Debian unstable (main) Status in coreutils package in Ubuntu: New Bug description: New coreutils features are missing in Ubuntu. Especially, "ls --time=birth" available since 8.32, and time of file creation in stat(1) on btrfs or ext4 fixed since 8.31. Please consider to incorporate these features at least into Ubuntu 20.10 (Groovy Gorilla). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1888046/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1868405] [NEW] Untranslatable "Monitor of ..."
Public bug reported: It is impossible to translate string "Monitor of %s". Please add gettext call here and export the string into the .pot template. https://git.launchpad.net/ubuntu/+source/pulseaudio/tree/src/pulsecore/sink.c?id=25a10a09f88d51bfd7d80574fa6c329086630531#n373 ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: focal i18n ** Tags added: focal i18n -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1868405 Title: Untranslatable "Monitor of ..." Status in pulseaudio package in Ubuntu: New Bug description: It is impossible to translate string "Monitor of %s". Please add gettext call here and export the string into the .pot template. https://git.launchpad.net/ubuntu/+source/pulseaudio/tree/src/pulsecore/sink.c?id=25a10a09f88d51bfd7d80574fa6c329086630531#n373 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1868405/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1860994] Re: Indicator menu is too wide
** Tags added: eoan -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1860994 Title: Indicator menu is too wide Status in indicator-datetime package in Ubuntu: New Bug description: The indicator's context menu does not appear to have a maximal width. This leads to an unattractive appearance when the show-events key in the com.canonical.indicator.datetime schema is true (default value) and there is an event with quite long name. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1860994/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1860994] Re: Indicator menu is too wide
Khurshid Alam, yes, it is MATE. Here is an Apport output, sorry I did not realize to attach it earlier. ** Attachment added: "Apport.log" https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1860994/+attachment/5323320/+files/Apport.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1860994 Title: Indicator menu is too wide Status in indicator-datetime package in Ubuntu: New Bug description: The indicator's context menu does not appear to have a maximal width. This leads to an unattractive appearance when the show-events key in the com.canonical.indicator.datetime schema is true (default value) and there is an event with quite long name. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1860994/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1860994] [NEW] Indicator menu is too wide
Public bug reported: The indicator's context menu does not appear to have a maximal width. This leads to an unattractive appearance when the show-events key in the com.canonical.indicator.datetime schema is true (default value) and there is an event with quite long name. ** Affects: indicator-datetime (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Screenshot at 2020-01-27 16-58-54.png" https://bugs.launchpad.net/bugs/1860994/+attachment/5323318/+files/%D0%A1%D0%BD%D0%B8%D0%BC%D0%BE%D0%BA%20%D1%8D%D0%BA%D1%80%D0%B0%D0%BD%D0%B0%20%D0%B2%202020-01-27%2016-58-54.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1860994 Title: Indicator menu is too wide Status in indicator-datetime package in Ubuntu: New Bug description: The indicator's context menu does not appear to have a maximal width. This leads to an unattractive appearance when the show-events key in the com.canonical.indicator.datetime schema is true (default value) and there is an event with quite long name. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1860994/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp