Re: [Bug 1815672] Re: "at now +240minutes" calcultes wrongly if passing through midnight
On 14.02.19 09:09, Karl Stenerud wrote: > OK, give it a shot with the rpi again once you have access to it. Once > we've got a solid repro case, we can figure out what the heck's going > wrong. > Hi again, sorry, I couldn't reach the rpi where the problem occurs. I can only reach it via ssh and it is >300 kilometers away. I tested on another one, but the error does not occur there. (Raspberry Pi 2 vs. 3) Due to the second issue described (that a second entry will execute one from the past) it might be that I don't have access to the rpi for weeks (next time I drive there), or maybe only every second day. I'm not sure. Please feel free to mark the bug accordingly meanwhile. I will write again as soon as I have news. Regards, Markus. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1815672 Title: "at now +240minutes" calcultes wrongly if passing through midnight To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at/+bug/1815672/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1815672] Re: "at now +240minutes" calcultes wrongly if passing through midnight
Hi, my scenario was: > echo "shutdown -h now" | at now +240minutes It is executed from /etc/rc.local at system startup. The difference I see that I used a Raspberry Pi. Maybe an ARM only issue? (Have no access to the affected Raspi for the next 4 days, so I cannot test more atm, sorry) Regards, Markus. Am 13. Februar 2019 10:24:31 MEZ schrieb Karl Stenerud : >Hi, > >I tried reproducing the error, but it didn't trigger for me: > >root@tester:~# date >Wed Feb 13 09:21:00 UTC 2019 >root@tester:~# at now +900minutes >warning: commands will be executed using /bin/sh >at> ls >at> >job 3 at Thu Feb 14 00:21:00 2019 >root@tester:~# atq >3 Thu Feb 14 00:21:00 2019 a root >root@tester:~# uname -a >Linux tester 4.15.0-45-generic #48-Ubuntu SMP Tue Jan 29 16:28:13 UTC >2019 x86_64 x86_64 x86_64 GNU/Linux >root@tester:~# lsb_release -rd >Description: Ubuntu 18.04.2 LTS >Release: 18.04 >root@tester:~# at -V >at version 3.1.19 > > >Could you put together a test case that will trigger every time? > > >** Changed in: at (Ubuntu) > Status: New => Incomplete > >-- >You received this bug notification because you are subscribed to the >bug >report. >https://bugs.launchpad.net/bugs/1815672 > >Title: > "at now +240minutes" calcultes wrongly if passing through midnight > >Status in at package in Ubuntu: > Incomplete > >Bug description: > > at --version > at version 3.1.19 > > uname -a >Linux pi3 4.4.38-v7+ #938 SMP Thu Dec 15 15:22:21 GMT 2016 armv7l >armv7l armv7l GNU/Linux > > lsb_release -rd > Description:Ubuntu 18.04.2 LTS > Release:18.04 > > Error description: >Let´s assume it is February, 12th, 10 pm and you want "at" to execute a >command 4 hours from now, so at February 13th, 2 am in the morning. >If running "at now +240minutes" now, this will result in the following >"atq": > 19 Tue Feb 12 02:00:00 2019 a root > > So it is "Feb 12" instead of "Feb 13". > >Even worse, if you add another command to the "at queue" now without >emptying it first, the original command in the queue will be executed >directly, because obviously at notices now that there is some command >to be executed from the past. >This can be annoying when e.g. shutting down a remote server 4 hours >after it has been powered up with "at". > >To manage notifications about this bug go to: >https://bugs.launchpad.net/ubuntu/+source/at/+bug/1815672/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1815672 Title: "at now +240minutes" calcultes wrongly if passing through midnight To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at/+bug/1815672/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1815672] [NEW] "at now +240minutes" calcultes wrongly if passing through midnight
Public bug reported: > at --version at version 3.1.19 > uname -a Linux pi3 4.4.38-v7+ #938 SMP Thu Dec 15 15:22:21 GMT 2016 armv7l armv7l armv7l GNU/Linux > lsb_release -rd Description:Ubuntu 18.04.2 LTS Release:18.04 Error description: Let´s assume it is February, 12th, 10 pm and you want "at" to execute a command 4 hours from now, so at February 13th, 2 am in the morning. If running "at now +240minutes" now, this will result in the following "atq": 19 Tue Feb 12 02:00:00 2019 a root So it is "Feb 12" instead of "Feb 13". Even worse, if you add another command to the "at queue" now without emptying it first, the original command in the queue will be executed directly, because obviously at notices now that there is some command to be executed from the past. This can be annoying when e.g. shutting down a remote server 4 hours after it has been powered up with "at". ** Affects: at (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/1815672 Title: "at now +240minutes" calcultes wrongly if passing through midnight To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at/+bug/1815672/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1500751] Re: Cryptsetup Keyboard not working on Xubuntu 3.19.0-30
After searching and trying for a long, long time, I finally found a solution which is acceptable for me. The situation is rather complex, so I try to describe it as structured as possible. Configuration - Hardware configuration: DH87RL board i7-4771 CPU GeForce GTX 970 Software configuartion: Ubuntu 15.10 Driver selection You can either go with the open nouveau driver which is installed by default, or use the proprieatary nvidia driver. Next, the "plymouth" package which enables you to configure the graphical boot up, is strongly involved. Using the nvidia driver together with plymouth does not work for me, but for all other 3 possible combinations, the solution is described below. There are 2 issues here closely connected, one is being able to enter the password for encrypted hard disks during boot, and the other is being able to switch to the console when X is up and running. Both issues are described below. Being able to enter the password for encrypted hard disks during boot - Nouveau driver with plymouth: The Nouveau driver works "ok" - this means I have to press the down arrow on the keyboard while booting so the text mode appears. There, the password is asked. (Some stars may already be displayed - delete them before entering the password...) This solution was ok, but I needed the nvidia driver to work, because with nouveau, for example, I had no proper 3D acceleration inside virtualbox. Nvidia driver without plymouth: The nvidia driver I use is nvidia-352 currently. I installed it via apt-get. So I did not download and install the driver from the nvidia.com site directly, but used the distribution (in my case: Ubuntu 15.10) package for the nvidia driver instead. For the nvidia driver to work, I had to disable plymouth. This can be done for example by passing the "noplymouth" option to the kernel parameters. --- /etc/default/grub (example) --- [...] GRUB_CMDLINE_LINUX_DEFAULT="quiet splash noplymouth" [...] --- update-grub --- Afterwards, execute update-grub from the command line: # update-grub With that changes, I can see the screen flicker shortly during the graphical boot (obviously the password prompt appearing for a fraction of a second, and then disappearing again). But now I know that the password prompt is there, and I can start to type the password. The prompt will reappear with the first character typed, having recognized the typed character already. If insecure whether the password prompt is ready or not, I can still press the down arrow as described above. Yes, that´s not a perfect solution - but after searching and trying for such a long, long time: At least it is working - and you can get used to it. Just out of curiosity, I also tried the nouveau driver with plymouth disabled: In that case it works much smoother, as the password prompt really appears and stays on the screen. So it seems the free nouveau driver is doing something better than the nvidia driver. I guess NVIDIA has some homework to do here! Swith to console With the nouveau driver, it is easily possible to switch to the console (CTRL-ALT-F1) With the nvidia-352 driver, switching to the console is NOT possible! Pressing CTRL-ALT-F1 just does nothing. A (n ugly) workaround I found for this is to restart the window manager from within your X session. Working for me with lightdm as windows manager, not tested for others. Please save all your open documents BEFORE doing this, as all applications of your X session will be killed: sudo service lightdm restart So again, the nouveau driver does this better than the official nvidia driver. I need to say that I´m really disappointed by NVIDIA about that! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1500751 Title: Cryptsetup Keyboard not working on Xubuntu 3.19.0-30 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1500751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1386005] Re: Password not accepted graphical boot for encrypted root system
After searching and trying for a long, long time, I finally found a solution which is acceptable for me. The situation is rather complex, so I try to describe it as structured as possible. Configuration - Hardware configuration: DH87RL board i7-4771 CPU GeForce GTX 970 Software configuration: Ubuntu 15.10 Driver selection You can either go with the open nouveau driver which is installed by default, or use the proprietary nvidia driver. Next, the "plymouth" package which enables you to configure the graphical boot up, is strongly involved. Using the nvidia driver together with plymouth does not work for me, but for all other 3 possible combinations, the solution is described below. There are 2 issues here closely connected, one is being able to enter the password for encrypted hard disks during boot, and the other is being able to switch to the console when X is up and running. Both issues are described below. Being able to enter the password for encrypted hard disks during boot - Nouveau driver with plymouth: The Nouveau driver works "ok" - this means I have to press the down arrow on the keyboard while booting so the text mode appears. There, the password is asked. (Some stars may already be displayed - delete them before entering the password...) This solution was ok, but I needed the nvidia driver to work, because with nouveau, for example, I had no proper 3D acceleration inside virtualbox. Nvidia driver without plymouth: The nvidia driver I use is nvidia-352 currently. I installed it via apt-get. So I did not download and install the driver from the nvidia.com site directly, but used the distribution (in my case: Ubuntu 15.10) package for the nvidia driver instead. For the nvidia driver to work, I had to disable plymouth. This can be done for example by passing the "noplymouth" option to the kernel parameters. --- /etc/default/grub (example) --- [...] GRUB_CMDLINE_LINUX_DEFAULT="quiet splash noplymouth" [...] --- update-grub --- Afterwards, execute update-grub from the command line: # update-grub With that changes, I can see the screen flicker shortly during the graphical boot (obviously the password prompt appearing for a fraction of a second, and then disappearing again). But now I know that the password prompt is there, and I can start to type the password. The prompt will reappear with the first character typed, having recognized the typed character already. If insecure whether the password prompt is ready or not, I can still press the down arrow as described above. Yes, that´s not a perfect solution - but after searching and trying for such a long, long time: At least it is working - and you can get used to it. Just out of curiosity, I also tried the nouveau driver with plymouth disabled: In that case it works much smoother, as the password prompt really appears and stays on the screen. So it seems the free nouveau driver is doing something better than the nvidia driver. I guess NVIDIA has some homework to do here! Switch to console With the nouveau driver, it is easily possible to switch to the console (CTRL-ALT-F1) With the nvidia-352 driver, switching to the console is NOT possible! Pressing CTRL-ALT-F1 just does nothing. A (n ugly) workaround I found for this is to restart the window manager from within your X session. Working for me with lightdm as windows manager, not tested for others. Please save all your open documents BEFORE doing this, as all applications of your X session will be killed: sudo service lightdm restart So again, the nouveau driver does this better than the official nvidia driver. I need to say that I´m really disappointed by NVIDIA about that! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1386005 Title: Password not accepted graphical boot for encrypted root system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1386005/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1530548] Re: passphrase input-box for encrypted disk is not shown
*** This bug is a duplicate of bug 1359689 *** https://bugs.launchpad.net/bugs/1359689 After searching and trying for a long, long time, I finally found a solution which is acceptable for me. The situation is rather complex, so I try to describe it as structured as possible. Configuration - Hardware configuration: DH87RL board i7-4771 CPU GeForce GTX 970 Software configuration: Ubuntu 15.10 Driver selection You can either go with the open nouveau driver which is installed by default, or use the proprietary nvidia driver. Next, the "plymouth" package which enables you to configure the graphical boot up, is strongly involved. Using the nvidia driver together with plymouth does not work for me, but for all other 3 possible combinations, the solution is described below. There are 2 issues here closely connected, one is being able to enter the password for encrypted hard disks during boot, and the other is being able to switch to the console when X is up and running. Both issues are described below. Being able to enter the password for encrypted hard disks during boot - Nouveau driver with plymouth: The Nouveau driver works "ok" - this means I have to press the down arrow on the keyboard while booting so the text mode appears. There, the password is asked. (Some stars may already be displayed - delete them before entering the password...) This solution was ok, but I needed the nvidia driver to work, because with nouveau, for example, I had no proper 3D acceleration inside virtualbox. Nvidia driver without plymouth: The nvidia driver I use is nvidia-352 currently. I installed it via apt-get. So I did not download and install the driver from the nvidia.com site directly, but used the distribution (in my case: Ubuntu 15.10) package for the nvidia driver instead. For the nvidia driver to work, I had to disable plymouth. This can be done for example by passing the "noplymouth" option to the kernel parameters. --- /etc/default/grub (example) --- [...] GRUB_CMDLINE_LINUX_DEFAULT="quiet splash noplymouth" [...] --- update-grub --- Afterwards, execute update-grub from the command line: # update-grub With that changes, I can see the screen flicker shortly during the graphical boot (obviously the password prompt appearing for a fraction of a second, and then disappearing again). But now I know that the password prompt is there, and I can start to type the password. The prompt will reappear with the first character typed, having recognized the typed character already. If insecure whether the password prompt is ready or not, I can still press the down arrow as described above. Yes, that´s not a perfect solution - but after searching and trying for such a long, long time: At least it is working - and you can get used to it. Just out of curiosity, I also tried the nouveau driver with plymouth disabled: In that case it works much smoother, as the password prompt really appears and stays on the screen. So it seems the free nouveau driver is doing something better than the nvidia driver. I guess NVIDIA has some homework to do here! Switch to console With the nouveau driver, it is easily possible to switch to the console (CTRL-ALT-F1) With the nvidia-352 driver, switching to the console is NOT possible! Pressing CTRL-ALT-F1 just does nothing. A (n ugly) workaround I found for this is to restart the window manager from within your X session. Working for me with lightdm as windows manager, not tested for others. Please save all your open documents BEFORE doing this, as all applications of your X session will be killed: sudo service lightdm restart So again, the nouveau driver does this better than the official nvidia driver. I need to say that I´m really disappointed by NVIDIA about that! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1530548 Title: passphrase input-box for encrypted disk is not shown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1530548/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1521305] Re: opening "Repositories" dialog doesn't open the dialog but suggests reloading package sources immediately
Get the same error behaviour with the same traceback. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1521305 Title: opening "Repositories" dialog doesn't open the dialog but suggests reloading package sources immediately To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/synaptic/+bug/1521305/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1191700] Re: [saucy] software-properties-gtk crashed with Exception NameHasNoOwner: Could not get owner of name 'com.ubuntu.SoftwareProperties'
This bug still occurs repeatably in Wily. The lines number of the traceback are a little bit different now. They match to bug #1521305 now. (which is most likely a duplicate of this) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1191700 Title: [saucy] software-properties-gtk crashed with Exception NameHasNoOwner: Could not get owner of name 'com.ubuntu.SoftwareProperties' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1191700/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
