[Touch-packages] [Bug 1407940] Re: whoopsie-preferences does nothing
I have the same problem in Ubuntu MATE 22.04.3: $ sudo whoopsie-preferences Acquired the name: com.ubuntu.WhoopsiePreferences And it just hangs, no window comes up. I used to have trouble starting applications as root under X.Org, so I tried the old incantation too: pkexec env DISPLAY=:0 XAUTHORITY=/home/rdiez/.Xauthority whoopsie- preferences But the result is the same. There is no user-interface element in Ubuntu MATE to open the Whoopsie configuration tool, so manually typing some command would be the only way. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1407940 Title: whoopsie-preferences does nothing Status in apport package in Ubuntu: Expired Bug description: Invoking `sudo whoopsie-preferences` does nothing but print an unhelpful error message to console. There should be a feedback of any king regardless of what the error is. The output is ** (process:13772): WARNING **: Could not get metrics: Key file does not have key 'report_metrics' initctl: Job failed to start Could not process configuration: Key file does not have key 'report_metrics' Could not process configuration: (null) Acquired the name: com.ubuntu.WhoopsiePreferences ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: apport 2.14.7-0ubuntu8 Uname: Linux 3.17.7-031707-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jan 6 12:38:59 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-01-03 (3 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: apport SystemImageInfo: current build number: 0 device name: channel: daily last update: Unknown UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1407940/+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 1953719] [NEW] logrotate.service fails because it starts before winbind.service
Public bug reported: I have started to play with Prometheus on my Ubuntu 20.04.3. You can configure Prometheus to alert you when a systemd service fails, and in this way I noticed a problem with the logrotate.service immediately after booting the system. I looked with Cockpit, and Cockpit was reporting logrotate.service as "Failed to start". This is the log for logrotate.service : 8<8<8< Dez 09 08:00:56 rdiez3 systemd[1]: Starting Rotate log files... Dez 09 08:00:58 rdiez3 logrotate[1760]: Can't find pid for destination 'winbindd' Dez 09 08:00:58 rdiez3 logrotate[1069]: error: error running non-shared postrotate script for /var/log/samba/log.winbindd of '/var/log/samba/log.winbindd ' Dez 09 08:00:58 rdiez3 systemd[1]: logrotate.service: Main process exited, code=exited, status=1/FAILURE Dez 09 08:00:58 rdiez3 systemd[1]: logrotate.service: Failed with result 'exit-code'. Dez 09 08:00:58 rdiez3 systemd[1]: Failed to start Rotate log files. 8<8<8< I then looked at winbind.service , which was fine: 8<8<8< Dez 09 08:01:01 rdiez3 systemd[1]: Starting Samba Winbind Daemon... Dez 09 08:01:01 rdiez3 systemd[1]: Started Samba Winbind Daemon. 8<8<8< But I noticed that winbind.service started after logrotate.service . I wonder whether this is a service dependency issue. I am using this PC only during normal working hours, and logrotate.timer is set to run at midnight, when the computer will never be turned on. The worry is that this problem could effectively cause the complete log rotation to stop working. ** Affects: logrotate (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to logrotate in Ubuntu. https://bugs.launchpad.net/bugs/1953719 Title: logrotate.service fails because it starts before winbind.service Status in logrotate package in Ubuntu: New Bug description: I have started to play with Prometheus on my Ubuntu 20.04.3. You can configure Prometheus to alert you when a systemd service fails, and in this way I noticed a problem with the logrotate.service immediately after booting the system. I looked with Cockpit, and Cockpit was reporting logrotate.service as "Failed to start". This is the log for logrotate.service : 8<8<8< Dez 09 08:00:56 rdiez3 systemd[1]: Starting Rotate log files... Dez 09 08:00:58 rdiez3 logrotate[1760]: Can't find pid for destination 'winbindd' Dez 09 08:00:58 rdiez3 logrotate[1069]: error: error running non-shared postrotate script for /var/log/samba/log.winbindd of '/var/log/samba/log.winbindd ' Dez 09 08:00:58 rdiez3 systemd[1]: logrotate.service: Main process exited, code=exited, status=1/FAILURE Dez 09 08:00:58 rdiez3 systemd[1]: logrotate.service: Failed with result 'exit-code'. Dez 09 08:00:58 rdiez3 systemd[1]: Failed to start Rotate log files. 8<8<8< I then looked at winbind.service , which was fine: 8<8<8< Dez 09 08:01:01 rdiez3 systemd[1]: Starting Samba Winbind Daemon... Dez 09 08:01:01 rdiez3 systemd[1]: Started Samba Winbind Daemon. 8<8<8< But I noticed that winbind.service started after logrotate.service . I wonder whether this is a service dependency issue. I am using this PC only during normal working hours, and logrotate.timer is set to run at midnight, when the computer will never be turned on. The worry is that this problem could effectively cause the complete log rotation to stop working. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1953719/+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 1568726] [NEW] iconv stdio buffering
Public bug reported: Tool "iconv" suffers from the stdio buffering problem described here: https://stackoverflow.com/questions/14472179/how-do-i-perform-a -streaming-character-conversion Basically, when piping to iconv in an interactive session, output stutters. Tool "stdbuf" does not help. From the page above: "But it looks like iconv is managing the buffering internally itself - it's nothing to do with the Linux pipe buffer." Solutions are described in this page: http://www.pixelbeat.org/programming/stdio_buffering/ iconv should have a command-line switch to help. From the page above: "Note tail's stdout buffer would also have this problem, but tail -f calls fflush on the stdout stream when new data is received to alleviate this (as do tcpdump -l, grep --line-buffered and sed --unbuffered for example)." ** Affects: eglibc (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to eglibc in Ubuntu. https://bugs.launchpad.net/bugs/1568726 Title: iconv stdio buffering Status in eglibc package in Ubuntu: New Bug description: Tool "iconv" suffers from the stdio buffering problem described here: https://stackoverflow.com/questions/14472179/how-do-i-perform-a -streaming-character-conversion Basically, when piping to iconv in an interactive session, output stutters. Tool "stdbuf" does not help. From the page above: "But it looks like iconv is managing the buffering internally itself - it's nothing to do with the Linux pipe buffer." Solutions are described in this page: http://www.pixelbeat.org/programming/stdio_buffering/ iconv should have a command-line switch to help. From the page above: "Note tail's stdout buffer would also have this problem, but tail -f calls fflush on the stdout stream when new data is received to alleviate this (as do tcpdump -l, grep --line-buffered and sed --unbuffered for example)." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1568726/+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
