[Bug 237251] Re: Does not generate random passwords

2008-09-30 Thread Henrik Holst
I have noticed the very same and have created a patch that solves it, I have sent the patch up to mainline as well. ** Attachment added: "make makepasswd use /dev/urandom instead of insecure rand()" http://launchpadlibrarian.net/18093559/makepasswd.c.patch -- Does not generate random passwor

[Bug 237251] Re: Does not generate random passwords

2008-10-01 Thread Henrik Holst
Please ignore my previous comment, I had this confused with a C program with the exact same name (makepasswd) that had the exact same bug :-| ** Attachment removed: "make makepasswd use /dev/urandom instead of insecure rand()" http://launchpadlibrarian.net/18093559/makepasswd.c.patch -- Does

[Bug 1845800] Re: xiccd consumes 100% CPU

2019-10-19 Thread Henrik Holst
I see the same problem on a freshly installed Xubuntu 19.10. I have seen it occur twice now over the course of two days. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845800 Title: xiccd consumes 1

[Bug 1887292] [NEW] crash on install

2020-07-12 Thread Henrik Holst
Public bug reported: fails to install using standard path login using LVM (no enc.). see attached logs ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.15 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zun

[Bug 1646192] Re: AppArmor mangles the "name" for services protected by systemd

2016-12-22 Thread Henrik Holst
Thanks, using the attached_disconnect flag in the ApparmorProfile for the second application worked! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1646192 Title: AppArmor mangles the "name" for serv

[Bug 1646192] Re: AppArmor mangles the "name" for services protected by systemd

2017-06-05 Thread Henrik Holst
** Changed in: mariadb-10.0 (Ubuntu) Status: New => Incomplete ** Changed in: mariadb-10.0 (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1646192 T

[Bug 1674930] [NEW] Amazon EC2 instances broken

2017-03-22 Thread Henrik Holst
Public bug reported: I have installed nvidia-367 package because it is required by the Amazon Ec2 instance type g2.2xlarge. They are using an older Nvidia card (GRID K520) which is supported by nvidia-367 driver. This driver does now install nvidia-375. That driver does not support the g2.2xlarge

[Bug 1705067] [NEW] system-local terminfo does not search /usr/share/terminfo as README says

2017-07-18 Thread Henrik Holst
Public bug reported: $ lsb_release -rd Description:Ubuntu 16.04.2 LTS Release:16.04 The file /etc/terminfo/README says This directory is for system-local terminfo descriptions. By default, ncurses will search ${HOME}/.terminfo first, then /etc/terminfo (this

[Bug 1481398] [NEW] Weka crashes on launch

2015-08-04 Thread Henrik Holst
Public bug reported: I have installed the "weka" package in Ubuntu 14.04 LTS 32-bit. When I try and launch the application from menu nothing happens. When I try and launch it from gnome-terminal I get this: tv@pugsley:~$ java -version java version "1.7.0_79" OpenJDK Runtime Environment (IcedTea

[Bug 1166812] Re: black screen 3.2.0-40-generic kernel

2013-04-11 Thread Henrik Holst
Same problem here with a Lenovo W500. I'm not using whole disc encryption however (but use an encrypted /home). I have tried the "Boot options" instructions but the screen goes to black before anything meaningful is written (also it gets black quite quickly). 3.2.0-39 works like a charm and 3.2.0-

[Bug 1166812] Re: black screen 3.2.0-40-generic kernel

2013-04-11 Thread Henrik Holst
Booting with "nomodeset" works but then the resolution gets fixed at a very low value. So this problem must have a connection with the Intel graphics driver. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bu

[Bug 1166812] Re: black screen 3.2.0-40-generic kernel

2013-05-02 Thread Henrik Holst
Same here on my Lenovo W500 with Intel drivers, 3.2.0-41-generic boots fine, regression gone. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1166812 Title: black screen 3.2.0-40-generic kernel To ma

[Bug 1161227] Re: After update from 3.2.0-39 - BLACK SCREEN

2013-05-02 Thread Henrik Holst
*** This bug is a duplicate of bug 1166812 *** https://bugs.launchpad.net/bugs/1166812 Try the new 3.2.0.41-generic, it removed the regression for me and a lot of others! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bug

[Bug 1169304] Re: 3.2.0-40-generic hanging Lenovo T420 on boot

2013-04-17 Thread Henrik Holst
I have the very same problem with a Lenovo W500 using the Intel GPU (do however get a black screen 100% of the time), and I've tested the bisection kernel and it did not work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bug

[Bug 1166812] Re: black screen 3.2.0-40-generic kernel

2013-04-17 Thread Henrik Holst
Don't know if it's of any interest but mainline did not fix it for me either (Lenovo W500 with Intel GPU). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1166812 Title: black screen 3.2.0-40-generic

[Bug 750437] Re: fglrx hard lockup on shutdown

2011-11-07 Thread Henrik Holst
Same problem here with a Radeon 4870 on Ubuntu 11.10 (and had the error in 10.04, 10.10 and 11.04 as well), have the same kernel crash as fireandfuel reported: [ 128.680139] BUG: unable to handle kernel paging request at c900110f1000 [ 128.690008] IP: [] firegl_sig_notifier+0x4/0x40 [fglrx] -

[Bug 613040] Re: epstopdf has no #! line, can't be invoked by scripts (Debian patch available)

2011-03-24 Thread Henrik Holst
This bug is still present in natty (even though the application has moved to the texlive-font-utils package), and the Debian patch which is adding the shebang also works, so could the maintainer please add this patch soon. Or are we waiting for upstream to fix this? -- You received this bug notif