Steps to replicate:
1. Terminate ayatana-indicator-datetime-service.
2. Run in terminal:
$ LC_TIME=pl_PL.UTF-8 /usr/libexec/ayatana-indicator-datetime
/ayatana-indicator-datetime-service
** Summary changed:
- Wrong time display in Mate 20.10 on Raspberry Pi 4
+ Wrong time display in Ubuntu
The same happened on my two PC machines after upgrade from Ubuntu 20.04
to 20.10. I don't think that this is a problem with truncated display,
as the time next to time zone localization is also displayed this way
(see the attached screenshot).
** Attachment added: "169584345_146010740779649_388742
Tested 1.16.5 version, the bug is fixed.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1511259
Title:
Session child does not in
> I assume it's because they removed the x11 virtualbox package from the
LiveCD.
I don't think so. Virtualbox guest additions are needed only for
advanced features, like seamless desktop integration.
Moreover switching back and forth to tty7 fixes the problem.
--
You received this bug notificat
Public bug reported:
Steps to reproduce:
1. Go into the system settings and change theme to another one which has
different nm icon (for example change from Ambiance to Radiance).
2. Old nm-applet icon stays in tray.
3. Reconnect to the network. The new icon is loaded now.
** Affects: network-m
I also attach my instrumented sendsig script file.
** Attachment added: "S20sendsigs"
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1212142/+attachment/4178849/+files/S20sendsigs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
Screenshot of my delayed shutdown. I set number of loop iterations to 3
in order to fit whole sendsigs output on screen.
** Attachment added: "delayed_shutdown.jpg"
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1212142/+attachment/4178848/+files/delayed_shutdown.jpg
--
You received
** Summary changed:
- Slow shutdown/restart on saucy with sendsigs waiting 10 seconds
+ Slow shutdown/restart with sendsigs waiting 10 seconds
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1212142
Ti
I experience the same bug on precise. Adding sleep 2 after sync (not
before like @vim-i wrote above) helps.
I figured out that the problem is that when:
killall5 -15 $OMITPIDS # SIGTERM
is called, `initctl emit plymouth-ready` process is not alive yet, so it
does not receive SIGTERM. (I chec
** Tags added: precise
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1212142
Title:
Slow shutdown/restart on saucy with sendsigs waiting 10 seconds
To manage notifications about this bug go to:
htt
10 matches
Mail list logo
