[Bug 1330252] Re: ubuntu 14.04 ltsp-server /etc/X11/Xsession.d/40-ltsp-server DESKTOP_SESSION breaks lubuntu-desktop login

2015-05-06 Thread Tenho Tuhkala
Running dpkg-reconfigure dash and answering No  at server side fixed
this for me.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1330252

Title:
  ubuntu 14.04 ltsp-server /etc/X11/Xsession.d/40-ltsp-server
  DESKTOP_SESSION breaks lubuntu-desktop login

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ltsp/+bug/1330252/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1185756] Re: drbd8-utils not compatible with linux-lts-raring kernel in 12.04

2013-09-11 Thread Tenho Tuhkala
This bug should affect drbd8-utils as well because that is the one what
should be upgraded/fixed.

** Package changed: linux-lts-raring (Ubuntu) => drbd8 (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1185756

Title:
  drbd8-utils not compatible with linux-lts-raring kernel in 12.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/drbd8/+bug/1185756/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1381383] [NEW] Vm destroyed when created virsh create without --autodestroy

2014-10-15 Thread Tenho Tuhkala
Public bug reported:

Ubuntu 14.04.1 LTS and 12.04 LTS
 
libvirt-bin 1.2.2-0ubuntu13.1.5 and 0.9.8-2ubuntu17.20

Creating vm from dumped xml with command: virsh create vm.xml
Runs fine until domain shut down.

Expected to happen:
Domain to remain permanent when shut down.

What happened:
Domain destroyed right after shut down.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: libvirt-bin 1.2.2-0ubuntu13.1.5
ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
Uname: Linux 3.13.0-37-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: amd64
CurrentDesktop: GNOME
Date: Wed Oct 15 10:28:46 2014
InstallationDate: Installed on 2014-05-08 (159 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
SourcePackage: libvirt
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.libvirt.qemu.conf: [inaccessible: [Errno 13] Permission 
denied: '/etc/libvirt/qemu.conf']

** Affects: libvirt (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug trusty

** Attachment added: "XML used in testing."
   https://bugs.launchpad.net/bugs/1381383/+attachment/4236682/+files/vm.xml

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1381383

Title:
  Vm destroyed when created virsh create without --autodestroy

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1381383/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1381383] Re: Vm destroyed when created virsh create without --autodestroy

2014-10-17 Thread Tenho Tuhkala
So if I dump vm from other host and try to import it to other I need to
edit it to make stay persistent after poweroff? You can't know it if
it's run for a while (with poweroffs and ons) in host 1 and then you
move it to host 2 and it starts behaving like that.

As you might know, that's it a default setting of vm and not a adjustable 
setting in virt-manager nor virsh without editing directly xml in virsh or 
otherwise, so you can't rely admin knows it's needed to be edited to make vm 
not be destroyed after shutdown. 
I still think it as a bug because of that.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1381383

Title:
  Vm destroyed when created virsh create without --autodestroy

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1381383/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1381383] Re: Vm destroyed when created virsh create without --autodestroy

2014-10-20 Thread Tenho Tuhkala
** Attachment added: "Virsh commands and output"
   
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1381383/+attachment/4240355/+files/virsh-command.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1381383

Title:
  Vm destroyed when created virsh create without --autodestroy

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1381383/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1381383] Re: Vm destroyed when created virsh create without --autodestroy

2014-10-20 Thread Tenho Tuhkala
I made little examination about this issue and full console output, which says 
about all, is attached. 
So create -command doesn't set Persistent flag to true and doesn't create 
related xml to under /etc/libvirt/qemu/ no matter is --autodestroy used or not 
where as define -command sets Persistent flag and creates xml under directory. 

And is there really use for two commands to do the same thing but (not
so) different way?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1381383

Title:
  Vm destroyed when created virsh create without --autodestroy

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1381383/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1381383] Re: Vm destroyed when created virsh create without --autodestroy

2014-10-20 Thread Tenho Tuhkala
This is not really about virt-install nor virt-manager (other listed virtual 
machines are created with it), it's about how virsh handles vm creation from 
xml. With define -command it stays at it should, with create -command it stays 
only when virsh is connected and/or vm is running, which behaviour isn't 
described anywhere and thus I considered as a bug in virsh. 
As you can see from grep, all other vm got in on_poweroff -tag destroy as well 
and they stay persistent because they got a appropriate flag set. virsh create 
doesn't set it as it should according to the manual, or there's misinformation 
about this in manual.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1381383

Title:
  Vm destroyed when created virsh create without --autodestroy

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1381383/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1185756] Re: drbd8-utils not compatible with linux-lts-raring kernel in 12.04

2013-10-14 Thread Tenho Tuhkala
Sorry for delay, had another rush to work on. Fix posted in #17 works
fine in my set. Thank you.

mailtest-1:~$ uname -a
Linux mailtest-1 3.8.0-31-generic #46~precise1-Ubuntu SMP Wed Sep 11 18:21:16 
UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

mailtest-1:~$ drbdadm --version
DRBDADM_BUILDTAG=GIT-hash:\ 89a294209144b68adb3ee85a73221f964d3ee515\ build\ 
by\ phil@fat-tyre\,\ 2013-02-05\ 15:35:49
DRBDADM_API_VERSION=1
DRBD_KERNEL_VERSION_CODE=0x080402
DRBDADM_VERSION_CODE=0x080403
DRBDADM_VERSION=8.4.3

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1185756

Title:
  drbd8-utils not compatible with linux-lts-raring kernel in 12.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/drbd8/+bug/1185756/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1006321] [NEW] Generates same password multiple times

2012-05-30 Thread Tenho Tuhkala
Public bug reported:

System
Description:Ubuntu 12.04 LTS
Release:12.04

passwordmaker-cli version: 1.5+dfsg-1

Expected to happen:
Unique password generated in every run when no options or Master Password given.

What happened:
Same password generated in every run when no options or Master Password given.

Reproducible: Always.

** Affects: passwordmaker-cli (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/1006321

Title:
  Generates same password multiple times

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/passwordmaker-cli/+bug/1006321/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 458444] Re: dvb-usb-af9015 should be updated to the latest version to resolve some issues

2011-12-14 Thread Tenho Tuhkala
I got same problem as #49 and #50 with three of 15a4:9016 Afatech Technologies, 
Inc. AF9015 DVB-T USB2.0 sticks
After day or two dvb modules causes segfault and dies. Only rebooting helps, 
but I'd like to find more sophisticated solution for this.
System is Ubuntu 11.10 LTSP and kernel is 3.0.0-14-generic #23-Ubuntu SMP

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/458444

Title:
  dvb-usb-af9015 should be updated to the latest version to resolve some
  issues

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware-nonfree/+bug/458444/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 845700] Re: ltsp-update-image does not respect BOOTPROMPT_OPTIONS in config file

2011-12-15 Thread Tenho Tuhkala
Having same issue and seems like it doesn't respect any other setting
specified in file.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/845700

Title:
  ltsp-update-image does not respect BOOTPROMPT_OPTIONS in config file

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ltsp/+bug/845700/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 371072] Re: fetchmailconf does not start

2010-10-26 Thread Tenho Tuhkala
It is still broken in Maverick.

-- 
fetchmailconf does not start
https://bugs.launchpad.net/bugs/371072
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs