I know this is not the most world-shattering bug, but any chance we
could see a fix for this?
primes still (in 2016!) shows composites, which can be seen by doing:
=$ primes 35198908481059600 35198908481059602
35198908481059601
=$ factor 35198908481059601
35198908481059601: 181399 405277 478787
Public bug reported:
I installed KUbuntu 15.04 on fresh system. Then I added some scripts to
autostart, using:
- system settings
- workspace
- startup and shutdown
- autostart
- add script
The scripts have been correctly symlinked in $HOME/.config/autostart/
but after closing and reopening syste
Public bug reported:
I installed KUbuntu 15.04 on fresh system, and noticed that when I make
a session, and assign keyboard shortcut to run this session (like ctrl-
shift-t runs new "Shell') - it works, as long as the shortcut doesn't
use windows key.
I can enter such shortcut, and it's displayed
Public bug reported:
I just installed KUbuntu 15.04. One of the things I don't use is
KDEWallet.
In system settings there is no wallet configuration. It is still
available when ran using:
`kcmshell4 kwalletconfig`
but it would be better to have it available in normal settings app.
** Affects:
With these packages installed:
=# dpkg -l | awk '$1=="ii" && $2 ~ /^linux/ {printf "%-33s : %s\n", $2, $3}'
linux-firmware: 1.38
linux-headers-2.6.35-23 : 2.6.35-23.41
linux-headers-2.6.35-23-generic : 2.6.35-23.41
linux-headers-generic : 2.6.35.23.25
li
I have setup where I put clients in chroots, each client has it's own
chroot. has been running on jaunty, and everything was great.
Now I upgraded one chroot to lucid, and I can't start services in client
chroot:
[chroot] # /etc/init.d/atd start
Rather than invoking init scripts through /etc/init
I have same board. I do not use fakeroot, but I do use software raid.
Have 5 drives attached to intel controller, and 2 to marvell. On kernel
2.6.35-22 there is no track of marvell-attached drives, which makes the machine
stop booting (raid is on all disks, and is mounted on /home and /usr
When
