from:"Valentijn Sessink"

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1824615/+attachment/5255420/+files/ProcCpuinfoMinimal.txt

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

Title:
  lockups since version 2:4.7.6+dfsg~ubuntu-0ubuntu2.9

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

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

[Bug 1824615] SmbLog.txt

apport information

** Attachment added: "SmbLog.txt"
   https://bugs.launchpad.net/bugs/1824615/+attachment/5255423/+files/SmbLog.txt

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

Title:
  lockups since version 2:4.7.6+dfsg~ubuntu-0ubuntu2.9

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

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

[Bug 1824615] SambaInstalledVersions.txt

apport information

** Attachment added: "SambaInstalledVersions.txt"
   
https://bugs.launchpad.net/bugs/1824615/+attachment/5255422/+files/SambaInstalledVersions.txt

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

Title:
  lockups since version 2:4.7.6+dfsg~ubuntu-0ubuntu2.9

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

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

[Bug 1824615] ProcEnviron.txt

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1824615/+attachment/5255421/+files/ProcEnviron.txt

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

Title:
  lockups since version 2:4.7.6+dfsg~ubuntu-0ubuntu2.9

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

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

[Bug 1824615] Re: lockups since version 2:4.7.6+dfsg~ubuntu-0ubuntu2.9

apport information

** Tags added: apport-collected bionic

** Description changed:

  Since version 2:4.7.6+dfsg~ubuntu-0ubuntu2.9 / Ubuntu 18.04.1 LTS, smbd
  locks up sometimes. We are unsure why. No messages in the log.smbd.
  
  Symptoms: clients (a few, about 5 to 10, OSX and Linux machines)
  sometimes just cannot connect to Samba anymore. They call us, "the
  server doesn't work".
  
  Log messages: none that we are alarmed by (smb.conf log level = 1)
  
  Then, trying to restart samba (systemctl restart smbd.service) says:
  
  Apr 12 14:23:37 kantoor systemd[1]: Stopping Samba SMB Daemon...
  [...]
  Apr 12 14:25:07 kantoor systemd[1]: smbd.service: State 'stop-final-sigterm' 
timed out. Killing.
  Apr 12 14:25:07 kantoor systemd[1]: smbd.service: Killing process 29016 
(smbd) with signal SIGKILL.
  Apr 12 14:25:07 kantoor systemd[1]: smbd.service: Killing process 29017 
(smbd) with signal SIGKILL.
  Apr 12 14:25:07 kantoor systemd[1]: smbd.service: Killing process 29034 
(smbd) with signal SIGKILL.
  Apr 12 14:25:07 kantoor systemd[1]: smbd.service: Killing process 29035 
(smbd) with signal SIGKILL.
  Apr 12 14:25:07 kantoor systemd[1]: smbd.service: Killing process 29046 
(smbd) with signal SIGKILL.
  Apr 12 14:25:07 kantoor systemd[1]: smbd.service: Killing process 29047 
(smbd) with signal SIGKILL.
  Apr 12 14:25:07 kantoor systemd[1]: smbd.service: Killing process 29048 
(smbd) with signal SIGKILL.
  Apr 12 14:25:07 kantoor systemd[1]: smbd.service: Killing process 29049 
(smbd) with signal SIGKILL.
  Apr 12 14:25:07 kantoor systemd[1]: smbd.service: Killing process 29067 
(smbd) with signal SIGKILL.
  Apr 12 14:25:07 kantoor systemd[1]: smbd.service: Killing process 29068 
(smbd) with signal SIGKILL.
  Apr 12 14:25:07 kantoor systemd[1]: smbd.service: Killing process 29077 
(smbd) with signal SIGKILL.
  Apr 12 14:25:07 kantoor systemd[1]: smbd.service: Killing process 29078 
(smbd) with signal SIGKILL.
  Apr 12 14:25:07 kantoor systemd[1]: smbd.service: Killing process 29487 
(smbd) with signal SIGKILL.
  Apr 12 14:25:07 kantoor systemd[1]: smbd.service: Killing process 29749 
(smbd) with signal SIGKILL.
  Apr 12 14:25:07 kantoor systemd[1]: smbd.service: Killing process 29784 
(smbd) with signal SIGKILL.
  Apr 12 14:25:07 kantoor systemd[1]: smbd.service: Killing process 29793 
(smbd) with signal SIGKILL.
  Apr 12 14:25:07 kantoor systemd[1]: smbd.service: Failed with result 
'timeout'.
  Apr 12 14:25:07 kantoor systemd[1]: Stopped Samba SMB Daemon.
  Apr 12 14:25:07 kantoor systemd[1]: Starting Samba SMB Daemon...
  
  While a regular restart, when there are no complaints about "the server isn't 
working", just goes in sub-second time, like this morning:
  Apr 13 10:09:17 kantoor systemd[1]: Stopping Samba SMB Daemon...
  Apr 13 10:09:17 kantoor systemd[1]: Stopped Samba SMB Daemon.
  Apr 13 10:09:17 kantoor systemd[1]: Starting Samba SMB Daemon...
  Apr 13 10:09:17 kantoor systemd[1]: Started Samba SMB Daemon.
  Apr 13 10:09:17 kantoor smbd[14174]: [2019/04/13 10:09:17.107277,  0] 
../lib/util/become_daemon.c:124(daemon_ready)
  Apr 13 10:09:17 kantoor smbd[14174]:   STATUS=daemon 'smbd' finished starting 
up and ready to serve connections
  
  Would it help to try to attach "strace -p ... -p ..." for the smbd
  processes next time the lockup happens? Or do we need another log level?
  
  The smb.conf is fairly straightforward (maybe a bit oldfashioned):
  [global]
  log level = 1
  workgroup = hssa
  passdb backend  = ldapsam:ldap://127.0.0.1/
  ldap admin dn   = cn=admin,dc=kantoor,dc=hssa,dc=nl
  ldap ssl= off
  ldap suffix = dc=kantoor,dc=hssa,dc=nl
  ldap user suffix= ou=Users
  ldap group suffix   = ou=Groups
  ldap machine suffix = ou=Computers
  unix extensions = yes
  delete readonly = yes
  ea support  = yes
  ldap password sync  = yes
  interfaces = 127.0.0.0/8 ens3
  bind interfaces only = true
  load printers = no
  printing = bsd
  printcap name = /dev/null
  disable spoolss = Yes
  disable netbios = yes
  smb ports = 445
  dns proxy = no
  vfs objects = fruit streams_xattr
  security = user
  
  [homes]
  comment = Home Directories
  writable= yes
  
  [hssa]
  force group = users
  force directory mode= 2770
  force create mode   = 0660
  directory mask  = 2770
  create mode = 0660
  comment = Algemeen
  writable= yes
  path= /home/hssa
  mangled names = no
  mangling char = _
  valid users = @users
  
  [hssa-intern]
  force group = hssaintern
  force directory mode= 2770
  force create mode   = 0660
  directory mask  = 2770
  create mode

[Bug 1824615] [NEW] lockups since version 2:4.7.6+dfsg~ubuntu-0ubuntu2.9

Public bug reported:

Since version 2:4.7.6+dfsg~ubuntu-0ubuntu2.9 / Ubuntu 18.04.1 LTS, smbd
locks up sometimes. We are unsure why. No messages in the log.smbd.

Symptoms: clients (a few, about 5 to 10, OSX and Linux machines)
sometimes just cannot connect to Samba anymore. They call us, "the
server doesn't work".

Log messages: none that we are alarmed by (smb.conf log level = 1)

Then, trying to restart samba (systemctl restart smbd.service) says:

Apr 12 14:23:37 kantoor systemd[1]: Stopping Samba SMB Daemon...
[...]
Apr 12 14:25:07 kantoor systemd[1]: smbd.service: State 'stop-final-sigterm' 
timed out. Killing.
Apr 12 14:25:07 kantoor systemd[1]: smbd.service: Killing process 29016 (smbd) 
with signal SIGKILL.
Apr 12 14:25:07 kantoor systemd[1]: smbd.service: Killing process 29017 (smbd) 
with signal SIGKILL.
Apr 12 14:25:07 kantoor systemd[1]: smbd.service: Killing process 29034 (smbd) 
with signal SIGKILL.
Apr 12 14:25:07 kantoor systemd[1]: smbd.service: Killing process 29035 (smbd) 
with signal SIGKILL.
Apr 12 14:25:07 kantoor systemd[1]: smbd.service: Killing process 29046 (smbd) 
with signal SIGKILL.
Apr 12 14:25:07 kantoor systemd[1]: smbd.service: Killing process 29047 (smbd) 
with signal SIGKILL.
Apr 12 14:25:07 kantoor systemd[1]: smbd.service: Killing process 29048 (smbd) 
with signal SIGKILL.
Apr 12 14:25:07 kantoor systemd[1]: smbd.service: Killing process 29049 (smbd) 
with signal SIGKILL.
Apr 12 14:25:07 kantoor systemd[1]: smbd.service: Killing process 29067 (smbd) 
with signal SIGKILL.
Apr 12 14:25:07 kantoor systemd[1]: smbd.service: Killing process 29068 (smbd) 
with signal SIGKILL.
Apr 12 14:25:07 kantoor systemd[1]: smbd.service: Killing process 29077 (smbd) 
with signal SIGKILL.
Apr 12 14:25:07 kantoor systemd[1]: smbd.service: Killing process 29078 (smbd) 
with signal SIGKILL.
Apr 12 14:25:07 kantoor systemd[1]: smbd.service: Killing process 29487 (smbd) 
with signal SIGKILL.
Apr 12 14:25:07 kantoor systemd[1]: smbd.service: Killing process 29749 (smbd) 
with signal SIGKILL.
Apr 12 14:25:07 kantoor systemd[1]: smbd.service: Killing process 29784 (smbd) 
with signal SIGKILL.
Apr 12 14:25:07 kantoor systemd[1]: smbd.service: Killing process 29793 (smbd) 
with signal SIGKILL.
Apr 12 14:25:07 kantoor systemd[1]: smbd.service: Failed with result 'timeout'.
Apr 12 14:25:07 kantoor systemd[1]: Stopped Samba SMB Daemon.
Apr 12 14:25:07 kantoor systemd[1]: Starting Samba SMB Daemon...

While a regular restart, when there are no complaints about "the server isn't 
working", just goes in sub-second time, like this morning:
Apr 13 10:09:17 kantoor systemd[1]: Stopping Samba SMB Daemon...
Apr 13 10:09:17 kantoor systemd[1]: Stopped Samba SMB Daemon.
Apr 13 10:09:17 kantoor systemd[1]: Starting Samba SMB Daemon...
Apr 13 10:09:17 kantoor systemd[1]: Started Samba SMB Daemon.
Apr 13 10:09:17 kantoor smbd[14174]: [2019/04/13 10:09:17.107277,  0] 
../lib/util/become_daemon.c:124(daemon_ready)
Apr 13 10:09:17 kantoor smbd[14174]:   STATUS=daemon 'smbd' finished starting 
up and ready to serve connections

Would it help to try to attach "strace -p ... -p ..." for the smbd
processes next time the lockup happens? Or do we need another log level?

The smb.conf is fairly straightforward (maybe a bit oldfashioned):
[global]
log level = 1
workgroup = hssa
passdb backend  = ldapsam:ldap://127.0.0.1/
ldap admin dn   = cn=admin,dc=kantoor,dc=hssa,dc=nl
ldap ssl= off
ldap suffix = dc=kantoor,dc=hssa,dc=nl
ldap user suffix= ou=Users
ldap group suffix   = ou=Groups
ldap machine suffix = ou=Computers
unix extensions = yes
delete readonly = yes
ea support  = yes
ldap password sync  = yes
interfaces = 127.0.0.0/8 ens3
bind interfaces only = true
load printers = no
printing = bsd
printcap name = /dev/null
disable spoolss = Yes
disable netbios = yes
smb ports = 445
dns proxy = no
vfs objects = fruit streams_xattr
security = user

[homes]
comment = Home Directories
writable= yes

[hssa]
force group = users
force directory mode= 2770
force create mode   = 0660
directory mask  = 2770
create mode = 0660
comment = Algemeen
writable= yes
path= /home/hssa
mangled names = no
mangling char = _
valid users = @users

[hssa-intern]
force group = hssaintern
force directory mode= 2770
force create mode   = 0660
directory mask  = 2770
create mode = 0660
comment = HSSA-intern
writable= yes
path= /home/hssa intern
mangled names = yes
mangling char = _
valid users = @users

** Affects: samba (Ubuntu)
 Importance:

[Bug 1568050] Re: grub-install removes other EFI boot entries

2017-12-06 Thread Valentijn Sessink

The bug is somewhat worse than in the original report: grub-install will
remove anything that has "Ubuntu" (case INsensitive!) in it's name. In a
test, both "RAID Ubuntu /dev/sdc", "Ubuntu /dev/sdc" were removed by
grub-install. A label "RAID fallback /dev/sdc" would survive a call to
grub-install.

I'm not sure this is just a wishlist item. I can understand that grub-
install removes any item named "ubuntu" (case sensitive) because it
creates these. But why remove .*ubuntu.*/i ?

I agree with comment #4 that this is beyond most users.

Regarding comment #3: a sysadmin might want "ubuntu WDC_WD20EFRX-
68EUZN0_WD-WCC4M6HVCKR8", but for a regular user "ubuntu" may just be
fine. And having the disk ID automatically (i.e. by grub-install) added
to the menu means that it will also be automatically removed - adding to
complexity and to unintended side effects.

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

Title:
  grub-install removes other EFI boot entries

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

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

[Bug 1299041] Re: grub2-2.02 has wrong build-deps

2014-04-03 Thread Valentijn Sessink

Thanks for the = 1.10 addition.
Still, if you install ntfs-3g but not attr, then the ntfs_test FAILS - 
not skips - with an error ./grub-fs-tester: line 895: setfattr: command not 
found. It probably tests the availability of mkfs.ntfs somewhere without 
testing setfattr. You could argue that this is an upstream bug all by itself 
and has nothing to do with the build-deps. However, if there's a quick fix 
(and, in fact, why not let all tests succeed instead of skip?) it could be 
worth fixing this.

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

Title:
  grub2-2.02 has wrong build-deps

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

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

[Bug 1299041] Re: grub2-2.02 has wrong build-deps

2014-04-03 Thread Valentijn Sessink

Fair enough. (The reason I'm building it anyway is that grub2_2.02~beta2-7 
wouldn't install - so I could not get past the install phase - hence no 
accounts; hence build as root :-S
So thanks again for beta2-8 - it makes things much easier :-)

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

Title:
  grub2-2.02 has wrong build-deps

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

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

[Bug 1299041] Re: grub2-2.02 has wrong build-deps

2014-03-31 Thread Valentijn Sessink

Thanks - I'll recheck my build - problems after automake1.10 could be
due to wrong language settings.

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

Title:
  grub2-2.02 has wrong build-deps

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

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

[Bug 1298399] Re: grub-efi-amd64 2.02~beta2-7 fails to install on raid/lvm

Further research shows:
- a simple install with sda1 = fat32 EFI, sda2 = 100Gb ext4 does work
- an install with /dev/md0 formatted as ext4 root-fs fails
- an install with /dev/sda2 as LVM pv, with root as a volume within, fails too.

Both md and lvm installs initially seem to complain that grub-install
dummy failed. Trying to run grub-install from the command line will
then show the error about the missing load.cfg.

Rather weird is the fact that Bug #1236625 seems to describe the exact
same issue - but was fixed in grub2 - 2.00-19ubuntu2. Is this a
regression?

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

Title:
  grub-efi-amd64 2.02~beta2-7 fails to install on raid/lvm

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

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

[Bug 1299041] Re: grub2-2.02 has wrong build-deps

apport information

** Tags added: apport-collected trusty

** Description changed:

  after apt-get build-dep grub-efi-amd64, many packages are missing. The ones 
I tracked so far:
  automake1.10 (another automake is probably somewhere in the dependencies, but 
building complained that 1.10 is needed); to be able to run the tests, 
dependencies seem to be: lzop; hfsplus; squashfs-tools; attr; reiserfsprogs
  I might have missed a package - currently rebuilding grub and it seems to 
work.
+ --- 
+ ApportVersion: 2.13.3-0ubuntu1
+ Architecture: amd64
+ DistroRelease: Ubuntu 14.04
+ Package: grub2 (not installed)
+ ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6
+ Tags:  trusty
+ Uname: Linux 3.13.0-19-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups:
+  
+ _MarkForUpload: True

** Attachment added: ProcEnviron.txt
   
https://bugs.launchpad.net/bugs/1299041/+attachment/4048875/+files/ProcEnviron.txt

** Changed in: grub2 (Ubuntu)
   Status: Incomplete = Confirmed

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

Title:
  grub2-2.02 has wrong build-deps

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

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

[Bug 1299041] Re: grub2-2.02 has wrong build-deps

Jörg, I don't think the ProcEnviron.txt is the information you were
looking for. However, apt-get install apport; apt-get install python-
apport; apport-collect 1299041 did just that (on 14.04).

Now on a freshly installed 14.04, I ran the following:
# apt-get build-dep grub; apt-get build-dep grub-efi-amd64; apt-get source 
grub-efi-amd64
 cd grub2-2.02~beta2/; debian/rules build

After which an error pops up (among other make information):
configure.ac:48: require Automake 1.10.1, but have 1.9.6

If you only install automake1.10, more errors will pop up.  Now after issuing:
apt-get install lzop hfsplus squashfs-tools attr reiserfsprogs automake1.10
debian/rules build
... things work fine. (As a side note: I have to export LANG=C; LC_ALL=C but 
that could be due to wrongly setup locale and is unrelated to this bug).

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

Title:
  grub2-2.02 has wrong build-deps

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

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

[Bug 1298399] Re: grub-efi-amd64 2.02~beta2-7 fails to install on raid/lvm

# create a file /boot/grub/x86_64-efi/load.cfg with
search.fs_uuid 2ff0dd02-use-blkid-to-get-the-number-40cda0eb468d root
set prefix=($root)/boot/grub
# then use
chattr +i /boot/grub/x86_64-efi/load.cfg
# to make load.cfg write-protected (on an ext4 filesystem)
I'm still getting an error after restart, diskfilter writes are not supported 
press-a-key, but after a few seconds (and, luckily, without the key!) booting 
continues.

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

Title:
  grub-efi-amd64 2.02~beta2-7 fails to install on raid/lvm

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

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

[Bug 1299041] [NEW] grub2-2.02 has wrong build-deps

Public bug reported:

after apt-get build-dep grub-efi-amd64, many packages are missing. The ones I 
tracked so far:
automake1.10 (another automake is probably somewhere in the dependencies, but 
building complained that 1.10 is needed); to be able to run the tests, 
dependencies seem to be: lzop; hfsplus; squashfs-tools; attr; reiserfsprogs
I might have missed a package - currently rebuilding grub and it seems to work.

** Affects: grub2 (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/1299041

Title:
  grub2-2.02 has wrong build-deps

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

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

[Bug 1299041] Re: grub2-2.02 has wrong build-deps

That's why apt-get build-dep grub matters. Grub (not grub2) has a
Build-Depends: debhelper (= 4.0.0), automake1.9. Thus, automake1.9
gets installed. Grub2 doesn't even have a build-depend on automake -
there might be a lower dependency on automake but I did not check that.
So it's not a system from 2005, it's just that I typed apt-get build-
dep grub - as stated above.

The bottom line is: the build-dependencies of grub2 (which is in beta)
aren't fully up to date, and my list might be of help.

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

Title:
  grub2-2.02 has wrong build-deps

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

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

[Bug 1299041] Re: grub2-2.02 has wrong build-deps

s/grub2/grub2-2.02/ - the version that was added to 14.04 recently.

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

Title:
  grub2-2.02 has wrong build-deps

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

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

[Bug 1269992] Re: 2.02~beta2 requires manual testing

... also, build-depends of grub2-2.02 are not right, see bug #1299041
Required for building, but not in build-depends: lzop hfsplus squashfs-tools 
attr reiserfsprogs automake1.10

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

Title:
  2.02~beta2 requires manual testing

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

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

[Bug 1298399] [NEW] grub-efi-amd64 2.02~beta2-7 fails to install on raid/lvm

2014-03-27 Thread Valentijn Sessink

Public bug reported:

During installation of Trusty on a RAID6/LVM system, the installation fails 
during the configure phase of grub-efi-amd64. The installer message says 
GRUB installation failed
The 'grub-efi-amd64-signed' package failed to install into /target/. Without 
the GRUB boot loader, the installed system will not boot.

The installer log message screen says (among other things):
grub-install: error: cannot open `/boot/grub/x86_64-efi/load.cfg': No such file 
or directory.

After issuing:
chroot /target
grub-install -v
... the installation of grub also ends with:
grub-install: info: copying `/boot/grub/x86_64-efi/load.cfg' - 
`/boot/efi/EFI/ubuntu/grub.cfg'
grub-install: error: cannot open `/boot/grub/x86_64-efi/load.cfg': No such file 
or directory

Installation is on a raid6 (software-raid) device with lvm, /dev/mapper
/volumegroup-root1404 is the root-fs (ext4 formatted), there is a
separate EFI partition on /dev/sda. The disks are GPT-partitioned.

** Affects: grub2 (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/1298399

Title:
  grub-efi-amd64 2.02~beta2-7 fails to install on raid/lvm

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

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

[Bug 1269992] Re: 2.02~beta2 requires manual testing

2014-03-27 Thread Valentijn Sessink

This new bug
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1298399 is also on
trusty, with grub 2.02~beta2-7.

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

Title:
  2.02~beta2 requires manual testing

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

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

[Bug 1291321] Re: migration fails between 12.04 Precise and 14.04 Trusty

2014-03-21 Thread Valentijn Sessink

Unfortunately, no, that doesn't seem to work either. I managed to
compile qemu-kvm-1.0+noroms (required a few minor changes, linking with
librt and a documentation difference) and the supporting bios and pxe
files on Trusty. Migration now seems to work (Completed 100 %), but then
the target libvirt spews out a kvm: Features 0x10d4 unsupported.
Allowed features: 0x71000454 and the guest machine becomes non
responsive (feels like a disk issue) - a hard shutdown (aka destroy) -
on the target - is required, which makes the whole live migration effort
a bit silly :-S

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1291321

Title:
  migration fails between 12.04 Precise and 14.04 Trusty

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1291321] Re: migration fails between 12.04 Precise and 14.04 Trusty

2014-03-21 Thread Valentijn Sessink

Unfortunately, no, that doesn't seem to work either. I managed to
compile qemu-kvm-1.0+noroms (required a few minor changes, linking with
librt and a documentation difference) and the supporting bios and pxe
files on Trusty. Migration now seems to work (Completed 100 %), but then
the target libvirt spews out a kvm: Features 0x10d4 unsupported.
Allowed features: 0x71000454 and the guest machine becomes non
responsive (feels like a disk issue) - a hard shutdown (aka destroy) -
on the target - is required, which makes the whole live migration effort
a bit silly :-S

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

Title:
  migration fails between 12.04 Precise and 14.04 Trusty

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

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

Re: [Bug 1291321] Re: migration fails between 12.04 Precise and 14.04 Trusty

Ok, I understand. Please note that this was also an issue for 10.04 - 12.04, 
so it's definitely a good idea to have it fixed for future upgrades (aka 
trusty specific machine type).
I'm not sure about the extra qemu. The next action after migration would be to 
install the real qemu, right? After which I should stop-start (as opposed to 
re-start!) all VM's to make sure they're under a trusty-compatible qemu? Or an 
I missing something here?

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1291321

Title:
  migration fails between 12.04 Precise and 14.04 Trusty

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

Re: [Bug 1291321] Re: migration fails between 12.04 Precise and 14.04 Trusty

Otoh, now we're facing a non-migrateable 12.04 in general, because you cannot 
move your VMs out of the way :-(
Anyway, proper documentation is helpful in any case. Finally: there is no real 
workaround now, or is there? What would you do, having several 12.04 host 
machines? Just migrate everything with the VM's running?

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1291321

Title:
  migration fails between 12.04 Precise and 14.04 Trusty

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

Re: [Bug 1291321] Re: migration fails between 12.04 Precise and 14.04 Trusty

Ok, I understand. Please note that this was also an issue for 10.04 - 12.04, 
so it's definitely a good idea to have it fixed for future upgrades (aka 
trusty specific machine type).
I'm not sure about the extra qemu. The next action after migration would be to 
install the real qemu, right? After which I should stop-start (as opposed to 
re-start!) all VM's to make sure they're under a trusty-compatible qemu? Or an 
I missing something here?

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

Title:
  migration fails between 12.04 Precise and 14.04 Trusty

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

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

Re: [Bug 1291321] Re: migration fails between 12.04 Precise and 14.04 Trusty

Otoh, now we're facing a non-migrateable 12.04 in general, because you cannot 
move your VMs out of the way :-(
Anyway, proper documentation is helpful in any case. Finally: there is no real 
workaround now, or is there? What would you do, having several 12.04 host 
machines? Just migrate everything with the VM's running?

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

Title:
  migration fails between 12.04 Precise and 14.04 Trusty

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

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

[Bug 1291321] Re: migration fails between 12.04 Precise and 14.04 Trusty

Hi,

Adding qemu:commandline tags needs a namespace. What you do is:
12.04~# virsh edit machine
Now add the namespace. The resulting first line of the domain xml-file should 
read:
domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'
After that, adding qemu:commandline tags will work, but alas:

# virsh start fhdhvalentijn
error: Failed to start domain fhdhvalentijn
error: internal error Process exited while reading console log output: char 
device redirected to /dev/pts/12
kvm: Property 'cirrus-vga.vgamem_mb' not found

So 12.04 doesn't have the option. I even tried to trick the system into
thinking it did have a cirrus-vga.vgamem_mb thing, by 1) leaving the
option out; 2) starting fhdhvalentijn 3) virsh edit fhdhvalentijn and
adding the cirrus-option; then migrating the thing, but that doesn't
work either.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1291321

Title:
  migration fails between 12.04 Precise and 14.04 Trusty

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1291321] Re: migration fails between 12.04 Precise and 14.04 Trusty

Please note my comment #5: removing the vga adapter showed up a new
mismatch, this time for the virtio network adapter. I did not look into
that but you might want to check if there's more memory mismatches that
should be addressed before you start adding code.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1291321

Title:
  migration fails between 12.04 Precise and 14.04 Trusty

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1291321] Re: migration fails between 12.04 Precise and 14.04 Trusty

Please note my comment #5: removing the vga adapter showed up a new
mismatch, this time for the virtio network adapter. I did not look into
that but you might want to check if there's more memory mismatches that
should be addressed before you start adding code.

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

Title:
  migration fails between 12.04 Precise and 14.04 Trusty

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

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

[Bug 1291321] Re: migration fails between 12.04 Precise and 14.04 Trusty

Hi,

Adding qemu:commandline tags needs a namespace. What you do is:
12.04~# virsh edit machine
Now add the namespace. The resulting first line of the domain xml-file should 
read:
domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'
After that, adding qemu:commandline tags will work, but alas:

# virsh start fhdhvalentijn
error: Failed to start domain fhdhvalentijn
error: internal error Process exited while reading console log output: char 
device redirected to /dev/pts/12
kvm: Property 'cirrus-vga.vgamem_mb' not found

So 12.04 doesn't have the option. I even tried to trick the system into
thinking it did have a cirrus-vga.vgamem_mb thing, by 1) leaving the
option out; 2) starting fhdhvalentijn 3) virsh edit fhdhvalentijn and
adding the cirrus-option; then migrating the thing, but that doesn't
work either.

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

Title:
  migration fails between 12.04 Precise and 14.04 Trusty

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

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

[Bug 1291321] Re: migration fails between 12.04 Precise and 14.04 Trusty

Hi, is there anything I can do to help this bug's status?

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1291321

Title:
  migration fails between 12.04 Precise and 14.04 Trusty

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1291321] Re: migration fails between 12.04 Precise and 14.04 Trusty

When you add a machine with virt-manager, the display setting is model
type='cirrus' vram='9216' heads='1'/. I tried to set it to 10240 (which
is 10mb) but that didn't help - the error is the same.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1291321

Title:
  migration fails between 12.04 Precise and 14.04 Trusty

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1291321] Re: migration fails between 12.04 Precise and 14.04 Trusty

BTW, that last test was with the regular qemu-kvm in trusty, which is
1.7.0+dfsg-3ubuntu6. I upgraded to the ppa-version again and ... it
seems to do something. BRB.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1291321

Title:
  migration fails between 12.04 Precise and 14.04 Trusty

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1291321] Re: migration fails between 12.04 Precise and 14.04 Trusty

error: Unable to read from monitor: Connection reset by peer and the machine 
crashed :-(
Next try, same as always: Length mismatch: vga.vram: 100 in != 80
That's a weird side effect, sometimes not only migration fails, but the machine 
on the source host crashes, too. Did you reproduce that as well?

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1291321

Title:
  migration fails between 12.04 Precise and 14.04 Trusty

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1291321] Re: migration fails between 12.04 Precise and 14.04 Trusty

Hi, is there anything I can do to help this bug's status?

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

Title:
  migration fails between 12.04 Precise and 14.04 Trusty

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

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

[Bug 1291321] Re: migration fails between 12.04 Precise and 14.04 Trusty

When you add a machine with virt-manager, the display setting is model
type='cirrus' vram='9216' heads='1'/. I tried to set it to 10240 (which
is 10mb) but that didn't help - the error is the same.

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

Title:
  migration fails between 12.04 Precise and 14.04 Trusty

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

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

[Bug 1291321] Re: migration fails between 12.04 Precise and 14.04 Trusty

BTW, that last test was with the regular qemu-kvm in trusty, which is
1.7.0+dfsg-3ubuntu6. I upgraded to the ppa-version again and ... it
seems to do something. BRB.

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

Title:
  migration fails between 12.04 Precise and 14.04 Trusty

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

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

[Bug 1291321] Re: migration fails between 12.04 Precise and 14.04 Trusty

error: Unable to read from monitor: Connection reset by peer and the machine 
crashed :-(
Next try, same as always: Length mismatch: vga.vram: 100 in != 80
That's a weird side effect, sometimes not only migration fails, but the machine 
on the source host crashes, too. Did you reproduce that as well?

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

Title:
  migration fails between 12.04 Precise and 14.04 Trusty

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

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

Re: [Bug 1291321] Re: migration fails between 12.04 Precise and 14.04 Trusty

Hi,

Installed qemu-common qemu-keymaps qemu-kvm qemu-system-common
qemu-system-x86 qemu-utils from the ppa, same error:

source (12.04): # error: operation failed: migration job: unexpectedly
failed

Log file on target (14.04, log_level = 1) says:

2014-03-13 07:03:56.550+: starting up
LC_ALL=C
PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin
QEMU_AUDIO_DRV=none /usr/bin/kvm -name fhdhvalentijn -S -machine
pc-1.0,accel=kvm,usb=off -m 2048 -realtime mlock=off -smp
1,sockets=1,cores=1,threads=1 -uuid f46f2877-62b2-5c2c-0b76-f62e6773dbff
-no-user-config -nodefaults -chardev
socket,id=charmonitor,path=/var/lib/libvirt/qemu/fhdhvalentijn.monitor,server,nowait
-mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc
-no-shutdown -boot strict=on -kernel
/tmp/migrate/vmlinuz-2.6.32-53-generic -initrd
/tmp/migrate/initrd.img-2.6.32-53-generic -append root=/dev/vda ro
-device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive
file=/dev/mapper/OpenOffice-filmhuisrestorevalentijn,if=none,id=drive-virtio-disk0,format=raw
-device
virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1
-netdev tap,fd=24,id=hostnet0,vhost=on,vhostfd=25 -device
virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:b3:d1:57,bus=pci.0,addr=0x3
-chardev pty,id=charserial0 -device
isa-serial,chardev=charserial0,id=serial0 -vnc 127.0.0.1:0 -device
cirrus-vga,id=video0,bus=pci.0,addr=0x2 -incoming tcp:[::]:49152 -device
virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5
char device redirected to /dev/pts/1 (label charserial0)
Length mismatch: vga.vram: 100 in != 80
qemu: warning: error while loading state for instance 0x0 of device 'ram'
load of migration failed
2014-03-13 07:03:56.922+: shutting down

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1291321

Title:
  migration fails between 12.04 Precise and 14.04 Trusty

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1291321] Re: migration fails between 12.04 Precise and 14.04 Trusty

The 100 comes from vga.h in the source for qemu-kvm-1.0+noroms: #define 
VGA_RAM_SIZE (16 * 1024 * 1024)
I could not find the 80 value - as far as I can see, vga ram size is not 
fixed anymore in the qemu-1.7.0+dfsg source - but I did not fully understand 
the code.
Anyway, I tried something new and removed the video device from the machine. 
Now a new error pops up:
Length mismatch: :00:03.0/virtio-net-pci.rom: 1 in != 2

Anything else I can check?

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1291321

Title:
  migration fails between 12.04 Precise and 14.04 Trusty

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

Re: [Bug 1291321] Re: migration fails between 12.04 Precise and 14.04 Trusty

Hi,

Installed qemu-common qemu-keymaps qemu-kvm qemu-system-common
qemu-system-x86 qemu-utils from the ppa, same error:

source (12.04): # error: operation failed: migration job: unexpectedly
failed

Log file on target (14.04, log_level = 1) says:

2014-03-13 07:03:56.550+: starting up
LC_ALL=C
PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin
QEMU_AUDIO_DRV=none /usr/bin/kvm -name fhdhvalentijn -S -machine
pc-1.0,accel=kvm,usb=off -m 2048 -realtime mlock=off -smp
1,sockets=1,cores=1,threads=1 -uuid f46f2877-62b2-5c2c-0b76-f62e6773dbff
-no-user-config -nodefaults -chardev
socket,id=charmonitor,path=/var/lib/libvirt/qemu/fhdhvalentijn.monitor,server,nowait
-mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc
-no-shutdown -boot strict=on -kernel
/tmp/migrate/vmlinuz-2.6.32-53-generic -initrd
/tmp/migrate/initrd.img-2.6.32-53-generic -append root=/dev/vda ro
-device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive
file=/dev/mapper/OpenOffice-filmhuisrestorevalentijn,if=none,id=drive-virtio-disk0,format=raw
-device
virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1
-netdev tap,fd=24,id=hostnet0,vhost=on,vhostfd=25 -device
virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:b3:d1:57,bus=pci.0,addr=0x3
-chardev pty,id=charserial0 -device
isa-serial,chardev=charserial0,id=serial0 -vnc 127.0.0.1:0 -device
cirrus-vga,id=video0,bus=pci.0,addr=0x2 -incoming tcp:[::]:49152 -device
virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5
char device redirected to /dev/pts/1 (label charserial0)
Length mismatch: vga.vram: 100 in != 80
qemu: warning: error while loading state for instance 0x0 of device 'ram'
load of migration failed
2014-03-13 07:03:56.922+: shutting down

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

Title:
  migration fails between 12.04 Precise and 14.04 Trusty

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

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

[Bug 1291321] Re: migration fails between 12.04 Precise and 14.04 Trusty

The 100 comes from vga.h in the source for qemu-kvm-1.0+noroms: #define 
VGA_RAM_SIZE (16 * 1024 * 1024)
I could not find the 80 value - as far as I can see, vga ram size is not 
fixed anymore in the qemu-1.7.0+dfsg source - but I did not fully understand 
the code.
Anyway, I tried something new and removed the video device from the machine. 
Now a new error pops up:
Length mismatch: :00:03.0/virtio-net-pci.rom: 1 in != 2

Anything else I can check?

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

Title:
  migration fails between 12.04 Precise and 14.04 Trusty

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

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

[Bug 1291321] [NEW] migration fails between 12.04 Precise and 14.04 Trusty

Public bug reported:

We're trying to live migrate machine fhdhvalentijn to a server named ranja. 
This used to work perfectly when both systems ran 12.04 Precise. After 
upgrading the target machine (ranja) to Trusty, migration fails; sometimes, 
migration results in shutting down the VM.
Command: virsh migrate --live --copy-storage-all --verbose vhdhvalentijn 
qemu+ssh://ranja/system
Expected: live migration
Result: error: operation failed: migration job: unexpectedly failed

Logfile on server Ranja says:
Length mismatch: vga.vram: 100 in != 80
qemu: warning: error while loading state for instance 0x0 of device 'ram'
load of migration failed
2014-03-12 11:05:30.325+: shutting down

Logfile on server Duikboot (the host) sometimes suddenly says:
2014-03-12 11:18:25.645+: shutting down and then the VM is no
longer running.

I also tried to start the migration from 14.04 (virsh -c
qemu+ssh://duikboot/system migrate --live --copy-storage-all ...), and
also tried to leave out --live (and tried various options like
migrating with virt-manager). Also tried to migrate a virgin machine
(i.e. a newly created machine with default options) - to no avail.

I did not try to migrate directly with qemu - as I have no experience
with that.

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

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/1291321

Title:
  migration fails between 12.04 Precise and 14.04 Trusty

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

Re: [Bug 1291321] Re: migration fails between 12.04 Precise and 14.04 Trusty

Yes, that's possible. Should I install the ppa on source, target or
both?

V.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1291321

Title:
  migration fails between 12.04 Precise and 14.04 Trusty

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1291321] [NEW] migration fails between 12.04 Precise and 14.04 Trusty

Public bug reported:

We're trying to live migrate machine fhdhvalentijn to a server named ranja. 
This used to work perfectly when both systems ran 12.04 Precise. After 
upgrading the target machine (ranja) to Trusty, migration fails; sometimes, 
migration results in shutting down the VM.
Command: virsh migrate --live --copy-storage-all --verbose vhdhvalentijn 
qemu+ssh://ranja/system
Expected: live migration
Result: error: operation failed: migration job: unexpectedly failed

Logfile on server Ranja says:
Length mismatch: vga.vram: 100 in != 80
qemu: warning: error while loading state for instance 0x0 of device 'ram'
load of migration failed
2014-03-12 11:05:30.325+: shutting down

Logfile on server Duikboot (the host) sometimes suddenly says:
2014-03-12 11:18:25.645+: shutting down and then the VM is no
longer running.

I also tried to start the migration from 14.04 (virsh -c
qemu+ssh://duikboot/system migrate --live --copy-storage-all ...), and
also tried to leave out --live (and tried various options like
migrating with virt-manager). Also tried to migrate a virgin machine
(i.e. a newly created machine with default options) - to no avail.

I did not try to migrate directly with qemu - as I have no experience
with that.

** Affects: libvirt (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/1291321

Title:
  migration fails between 12.04 Precise and 14.04 Trusty

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

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

Re: [Bug 1291321] Re: migration fails between 12.04 Precise and 14.04 Trusty

Yes, that's possible. Should I install the ppa on source, target or
both?

V.

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

Title:
  migration fails between 12.04 Precise and 14.04 Trusty

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

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

[Bug 1213744] Re: thunderbird stopped displaying folders

2013-10-31 Thread Valentijn Sessink

Hmm. I can reproduce the issue by putting the following line in 
/etc/thunderbird/syspref.js:
pref(toolkit.telemetry.prompted, true);

However, if I set this in prefs.js in the user's profile, after a restart 
Thunderbird has changed this into
user_pref(toolkit.telemetry.prompted, 2);

Changing the syspref option to 2 instead of true seems to resolve
the issue.

Those that suffer from this bug, could you look into
/etc/thunderbird/syspref.js if it has any prefs enabled? (The default
file does not change anything).

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

Title:
  thunderbird stopped displaying folders

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

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

[Bug 1213744] Re: thunderbird stopped displaying folders

2013-10-31 Thread Valentijn Sessink

This is the related mozilla bug:
https://bugzilla.mozilla.org/show_bug.cgi?id=807848, and
https://bugzilla.mozilla.org/show_bug.cgi?id=842073 provides background
information and -noise.

** Bug watch added: Mozilla Bugzilla #807848
   https://bugzilla.mozilla.org/show_bug.cgi?id=807848

** Bug watch added: Mozilla Bugzilla #842073
   https://bugzilla.mozilla.org/show_bug.cgi?id=842073

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

Title:
  thunderbird stopped displaying folders

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

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

[Bug 1085957] Re: NSCD crashes with SIGABRT when using LDAP authentication

2013-01-23 Thread Valentijn Sessink

On my 64 bit system nscd still seems to work. Have you tried to invalidate the 
nscd caches?
nscd -i group; nscd -i passwd; nscd -i services

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

Title:
  NSCD crashes with SIGABRT when using LDAP authentication

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

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

[Bug 585209] Re: .odt and .ods open with fileroller instead of openoffice

2012-11-07 Thread Valentijn Sessink

This could be just a manifestation of bug #435719. Not sure though,
because the original report does not mention if /home is mounted on NFS.

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

Title:
  .odt and .ods open with fileroller instead of openoffice

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

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

[Bug 384852] Re: OpenOffice.org writer can't open ODT files from sftp folders

2012-11-07 Thread Valentijn Sessink

This could be just a manifestation of bug #435719. Not sure though,
because the original report does not mention if /home is mounted on NFS.

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

Title:
  OpenOffice.org writer can't open ODT files from sftp folders

To manage notifications about this bug go to:
https://bugs.launchpad.net/openoffice/+bug/384852/+subscriptions

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

[Bug 694188] Re: [Upstream] Office does not try to detect character set of CSV

2011-09-21 Thread Valentijn Sessink

The bug clearly states: When doing this with the OOo from 8.04LTS, or
with the official version from Openoffice.org, autodetection does it's
job.

Hence, this is NOT an upstream issue. It is a bug introduced by the
Ubuntu 10.04 packages.

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

Title:
  [Upstream] Office does not try to detect character set of CSV

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/694188/+subscriptions

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

[Bug 694188] Re: OpenOffice.org 3.2 does not try to detect character set of CSV

2011-03-04 Thread Valentijn Sessink

I don't understand the intended behaviour part. I don't think I should
file a bug in OpenOffice.org because autodetection does work correctly
there, or should I? ;-)

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

Title:
  OpenOffice.org 3.2 does not try to detect character set of CSV

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

[Bug 711770] [NEW] current pam setup ignores everything (for example: bad passwords, configuration problems)

2011-02-02 Thread Valentijn Sessink

*** This bug is a security vulnerability ***

Public security bug reported:

The current pam profiles mostly seem to say:

auth[success=$skipnum default=ignore]

This means that pam will happily try to validate your password against
all the modules there are; in fact, it ignores wrong passwords, it
ignores errors, acct_expired, maxtries, perm_denied and what not, in any
of the modules. Given enough pam modules, your chances of being able to
authorize could converge to 1 ;-)

This is the wrong way around. A user should be locked out if she is
locked out in any of the authentication databases; she should be denied
access if she guesses the wrong password in one of these databases.

There is a debian bug http://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=583492 that hints in this direction (in fact, it
suggests a seemingly more appropriate [success=ok new_authtok_reqd=done
ignore=ignore user_unknown=ignore authinfo_unavail=ignore default=bad]),
but this bug is not flagged as a security issue.

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

** Visibility changed to: Public

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

Title:
  current pam setup ignores everything (for example: bad passwords,
  configuration problems)

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

[Bug 711770] Re: current pam setup ignores everything (for example: bad passwords, configuration problems)

2011-02-02 Thread Valentijn Sessink

Ignoring everything, except success is the security issue.
I don't have anything against trying all modules, nor do I think that the one 
succeeding module is a security issue per se. But ignoring blatant errors, 
locked out users, wrong and/or expired passwords, that is a security issue.

May I kindly ask you to reconsider the ignoring part? After that,
please feel free to ignore this bug report as well ;-)

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

Title:
  current pam setup ignores everything (for example: bad passwords,
  configuration problems)

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

[Bug 691130] Re: PDF workflow flawed, crashes printers

This file crashes a Panasonic DP-C265, when printed under Maverick with
either Acroread, Evince or gtklp, print queue running on Lucid with
modifications as described earlier, to avoid PDF workflow. Will try to
fetch the PS file that is sent to the printer shortly.

** Attachment added: Crashes a Panasonic DP-C265
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/691130/+attachment/1791012/+files/Printcheck_DenHaag_week03.pdf

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

Title:
  PDF workflow flawed, crashes printers

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

[Bug 691130] Re: PDF workflow flawed, crashes printers

Is there a way in which I can send a PS file (as made from the
instructions at #18) to the printer, manually, through the IPP backend?
To double check if this still crashes the printer?

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

Title:
  PDF workflow flawed, crashes printers

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

[Bug 691130] Re: PDF workflow flawed, crashes printers

Done as suggested in comment #18:
added FileDevice True
cp /etc/cups/ppd/kleurenkopieerapparaat.ppd /tmp/pana.ppd
lpadmin -p printtofile -E -v file:/tmp/spoolfile.ps -P /tmp/pana.ppd
lp -d printtofile /tmp/Printcheck_DenHaag_week03.pdf

The resulting Postscript file is attached.

** Attachment added: resulting PS file from printing to file.
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/691130/+attachment/1791098/+files/spoolfile.ps

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

Title:
  PDF workflow flawed, crashes printers

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

[Bug 691130] Re: PDF workflow flawed, crashes printers

Thanks. I verified, that printing 
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/691130/+attachment/1791098/+files/spoolfile.ps
 on this Panasonic printer crashes the printer - although the printer does not 
restart, it says Machine Error - Call TEL. 0736402888 - which is the local 
service organisation; when I reset the printer remotely, it has a  Remove 
Misfed Paper message on it's display.
I also tried the other crashing PDF, and this one immediately restarts the 
printer (even while the remove misfed paper message is still there, so the 
printer apparently starts interpreting the PS even before the paper path is 
cleared). I'll send this postscript file by private mail.
So far, I haven't been able to do anything to the Ricoh printing problem, 
because these printers are in a more secure environment, and unfortunately, I 
can't access them remotely as easy.

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

Title:
  PDF workflow flawed, crashes printers

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

[Bug 691130] Re: PDF workflow flawed, crashes printers

Printing the file does *not* work with these changes. That is: if you
have these changes, and try to print non-duplex, the printer will
freeze. Printing duplex does work. Regarding the printer model: I'll get
back to you with the specific model, because, actually, it strikes me as
a bit odd that this would be a 4510.

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

Title:
  PDF workflow flawed, crashes printers

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

[Bug 691130] Re: PDF workflow flawed, crashes printers

Ahem. I did not read your comment too well. I will check your changes,
*then* get back.

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

Title:
  PDF workflow flawed, crashes printers

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

[Bug 691130] Re: PDF workflow flawed, crashes printers

BTW, is there a possibility to intercept the final PS stream that is
sent to the printer? Having an intermediate PDF that crashes in some
situations, but prints in other, is helpful, but a bit complicated as
well.

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

Title:
  PDF workflow flawed, crashes printers

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

Re: [Bug 691130] Re: PDF workflow flawed, crashes printers

Hi,

Op 07-01-11 20:47, georgeliu schreef:
 Yes, you can create a print-to-file queue using the same PPD file.

I'll implement that next week.

[...]
 In my previous posting (#14), I didn't want you to try anything new, I just 
 want to know how to reproduce the problem.
 Do I need to do the following as specified in your original posting?

Probably, yes. Because otherwise, as far as I understand, CUPS may use 
the new PDF workflow.

So:
- set mime.convs options as described
- restart CUPS if necessary (if I understand correctly, it calculates 
the print routing only during it's startup, but I may be wrong)
- easiest way is: have gtklp installed, please print the file with this, 
make sure you have duplex printing OFF.

Please note, that the file you have is the file as found in the print 
queue, so it's meant to be printed with lp or gtklp. If you reopen it 
with Acrobat or Evince, I'm not sure what it will get you - probably 
just a dull print.

Another new fact is, that the printer in question is a NRG MPC4500; 
we're only using the 4510 PS file, hence my confusion.

Please note, that because of the duplex/non duplex sensitivity, I'm 
still not 100% confident that of the reproducability of this problem, 
i.e. there may still be parts missing. Ulrich Wehner from Ricoh USA was 
able to crash some older printer, but not his regular MPC3500. So I hope 
that the print-to-file option will get us a Postscript file that will 
crash the printer directly.

Best regards,

Valentijn

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

Title:
  PDF workflow flawed, crashes printers

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

[Bug 691130] Re: PDF workflow flawed, crashes printers

2011-01-06 Thread Valentijn Sessink

I now have a verifyable PDF, straight from the print queue, that crashes
a certain Ricoh printer - a Ricoh Aficio AP4510 PS, which isn't exactly
your entry-level small printer - it's rated 45K pages per month.

The printer crash *only* happens when:
- we print the original document (a PDF) from Evince
- we have the printer output non-duplex (the default is to duplex)

If we set the print options to the default (i.e. duplex), no crash
occurs.

I have now personally verified this (no stupid users telling random
things in between). We verified the duplex or non duplex occurence
with both Evince (from the original document) and gtklp (with the
document that I grabbed from the queue). This gives me 4 new documents
in the queue, all bit-by-bit the same; they will have the printer crash
due to setting a non-duplex option.

Let me repeat that in pseudo-code:
Original.pdf - printed from Evince, duplex - CUPS queue: nocrash1.pdf -
prints
Original.pdf - printed from Evince, simplex - CUPS queue: crash1.pdf -
crashes printer
nocrash1.pdf - printed with gtklp, duplex - CUPS queue: nocrash2.pdf - prints
nocrash1.pdf - printed with gtklp, simplex - CUPS queue: crash2.pdf -
crashes printer

As a check/double/triple-check: nocrash1.pdf, crash1.pdf, nocrash2.pdf
and crash2.pdf are bit-by-bit the same, they all have the same md5sum,
so the printing options are at stake here.

Now the problem is: the document is not exactly for everyones eyes, i.e.
I would not like it to be generally available (through Launchpad, for
example).

On the other hand, it's not exactly Top Secret, so sharing it privately
with a couple of developers at Openprinting wouldn't hurt.

So my question is: can I send Till . Kamppeter at his Gmail.com account
a 546K PDF document that will crash a certain type of printer, when
certain printing options are active? Or is there a better place to send
such document?

I realise that this may end up being a bug in either Evince or the Ricoh
PS firmware, but I'd like at least to be able to know what that bug is.

** Attachment removed: PDF that will not print with the new PDF workflow

https://bugs.launchpad.net/ubuntu/+source/cups/+bug/691130/+attachment/1774777/+files/strick.pdf

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

Title:
PDF workflow flawed, crashes printers

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

[Bug 691130] Re: PDF workflow flawed, crashes printers

2011-01-06 Thread Valentijn Sessink

(I removed the previous attachment; sorry for the fuzz; I simply
couldn't reproduce the issue yesterday while I was at the customer's
premises, so I suspect a luser reporting nonsense).

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

Title:
  PDF workflow flawed, crashes printers

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

[Bug 691130] Re: PDF workflow flawed, crashes printers

2011-01-05 Thread Valentijn Sessink

Oh well. Please forget about this attachment. Never trust your end users
to tell you if anything did or did not work; as far as I can see, the
attached PDF just works (might have been a bit slower under 10.04, I'm
not sure). I still do have a PDF that crashes the printer - only if
printed from Evince, though. I'll send that shortly.

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

Title:
  PDF workflow flawed, crashes printers

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

[Bug 645448] Re: preferences in empathy doesn't get saved when home directory is on nfs

2010-12-28 Thread Valentijn Sessink

http://ubuntuforums.org/showthread.php?t=1646526 seems to suggest that
this is Inotify-related. That would mean that this is another
manifestation of the problem described in Bug #383118 (which is, in it's
own, a bit misguided as it's probably not Gamin, but the kernel that is
at fault, but I'm not sure).

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

Title:
  preferences in empathy doesn't get saved when home directory is on nfs

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

[Bug 561703] Re: Row height in xls is not saved

The bug is not present in the upstream 3.2.0 version (when installing
that on Ubuntu, that is), so it's an Ubuntu ( Debian?) specific bug.

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

Title:
  Row height in xls is not saved

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

[Bug 691130] Re: PDF workflow flawed, crashes printers

Unfortunately, with a Maverick installation, the long delay in printing
persists. Please note that this is not a live CD, but an installed
machine. On the other hand, the install is pretty basic and printing is
done through the network, so there is nothing the local Cups is doing.

Our *hacked* print path, on the central server:
application/postscript application/pdf 2 pstopdf
application/pdf application/vnd.cups-postscript 43  pdftops
application/postscript  application/vnd.cups-postscript 65  pstops

On a server with Ubuntu 10.04 LTS, this will output a certain PDF within
4 minutes on a Panasonic DP-C265 with Postscript module.

A regular print path (nothing changed), with the same PPD, on an
installed Maverick machine, a print takes considerably more time (more
than 15 minutes). I'm currently investigating if this PPD is public
(i.e. can be attached to this bug report).

One thing that puzzles me, is that I could not exactly see the
differences in the print path between 10.04 and 10.10: 10.04 seems to
use Poppler as well?

Anyway, please tell me what I should test next.

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

Title:
  PDF workflow flawed, crashes printers

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

[Bug 691130] Re: PDF workflow flawed, crashes printers

 [...] will output a certain PDF [...]
 than 15 minutes). I'm currently investigating if this PPD is public

That should read: if this PDF (the document I'm trying to print) is
public.

So, to summarize: a) printing from a Maverick machine to a Lucid server with 
hacked-up printing path: 4 minutes (prints to Panasonic printer through IPP).
b) Printing on the Maverick machine itself, straight to the same IPP addressed 
Panasonic printer takes considerably more time (we stopped waiting after 18 
minutes, printer still flashing, not sure if anything will come out today ;)

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

Title:
  PDF workflow flawed, crashes printers

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

[Bug 691130] Re: PDF workflow flawed, crashes printers

The attached PDF (which is public) will not print or print very slowly
(30 minutes) on the above printer with the Lucid/Maverick default print
path. With a hacked workflow as described, all pages print within 4
minutes.

** Attachment added: PDF that will not print with the new PDF workflow
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/691130/+attachment/1774777/+files/strick.pdf

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

Title:
  PDF workflow flawed, crashes printers

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

[Bug 691130] Re: PDF workflow flawed, crashes printers

I don't think I understand the Capturing print job data part of
DebuggingPrintingProblems. As far as I can see, disabling the printer
will stop the print queue handling *before* filtering jobs. So all I am
getting is the PDF that I already attached above. Am I doing something
wrong?

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

Title:
  PDF workflow flawed, crashes printers

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

[Bug 691130] Re: PDF workflow flawed, crashes printers

That is what I did. (Hence my confusion when the captured file came out
identical to the original file ;)

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

Title:
  PDF workflow flawed, crashes printers

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

[Bug 691130] [NEW] PDF workflow flawed, crashes printers

2010-12-16 Thread Valentijn Sessink

Public bug reported:

Binary package hint: cups

Under Ubuntu Lucid, the new PDF workflow in CUPS poses various problems
for various printers: jobs will either not print (and may crash the
printer) or print very slowly. These are reports from various
customers.

We have seen a bunch of Ricoh printers fail (killing the user interface
of the printer, a hard reset is necessary to be able to use the printer
again); notably a Ricoh Aficio AP4510 PS that crashes; and a Ricoh1224c
that sometimes does not print; a Panasonic printer, DP-C265 (printing
will sometimes suddenly reset the printer); but also other customers
complain about not being able to print anymore, on various brands of
printers (we've seen Brother and HP)

We heavily suspect the new PDF workflow in CUPS, as the following workaround 
works:
change /usr/share/cups/mime/mime.convs to say:
application/pdf application/vnd.cups-postscript 43  pdftops
application/postscript  application/vnd.cups-postscript 65  pstops

This, essentially, makes the workflow use Postscript again when either
PDF or Postscript is presented.

Unfortunately, a crashing printing interface does not normally tell why
it is crashing, so I suspect this bug to be quite hard to dig further
into. Somewhere between pstopdf, pdftopdf and cpdftocps, something goes
wrong. It may even be the file size (but I couldn't find any size
information in the ipp backend log messages that Cups sends out with
debug-logging enabled).

There are many bugs that may be related to this: bug #655422 (Sending
pdf and ps files to a printer routinely fails), Bug #665978 (Slow
Printing), Bug #667102 (Printing errors after upgrade).

** Affects: cups (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/691130

Title:
  PDF workflow flawed, crashes printers

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

Re: [Bug 691130] Re: PDF workflow flawed, crashes printers

2010-12-16 Thread Valentijn Sessink

Op 16-12-10 19:07, Till Kamppeter schreef:
 Your suggestion of modifiying the cost factors of the CUPS filters we
 have already applied in Maverick. Our implementation is a little
 different, we have only set
 application/postscript application/vnd.cups-postscript 65 pstops

I know. (See below).

 so that for a PostScript printer it is avoided to turn incoming
 PostScript into PDF and back into PostScript. If the incoming data is
 already PDF, there is not much difference whether one passes it through
 pdftopdf and then through pdftops or first through pdftops and then
 through pstops. The change especially eliminates PostScript to be turned

That's the theory. In practice, there *is* a difference.

 want to stay on LTS, please try also whether only setting

Yes we do.

 application/postscript application/vnd.cups-postscript 65 pstops
 in /usr/share/cups/mime/mime.convs already solves your problem. Please
 tell whether this works or only using

I did the trick with 65. But then customers complained that they could
not print PDF files, they sometimes would only print half, sometimes it
took very, very long. (I'm not sure if they would also crash the
printer) So that's why we also set the pdftops cost to 43.

So: only setting pstops to 65 does not solve the issue. My feeling is
that there's a problem within the filtering, one that's not easy to spot
but that pops up with the pstopdf stuff.

 SRU. Also try a Maverick live CD only to see whether Maverick has your
 problem solved without any additional changes.

It's only a couple of printers that crash, in live situations, with
print servers at customer premises. So it's a bit hard to check. I'll
see what I can do. Our own HP Laserjet doesn't crash, that's the main
problem ;-)

V.

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

Title:
  PDF workflow flawed, crashes printers

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

[Bug 575191] Re: simple-scan doesn't scan from HP M1522nf (MFP), while xsane works

2010-12-09 Thread Valentijn Sessink

** Changed in: simple-scan (Ubuntu)
   Status: Incomplete = Confirmed

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

Title:
  simple-scan doesn't scan from HP M1522nf (MFP), while xsane works

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

[Bug 670249] Re: no scanning result

2010-12-09 Thread Valentijn Sessink

*** This bug is a duplicate of bug 575191 ***
https://bugs.launchpad.net/bugs/575191

** This bug has been marked a duplicate of bug 575191
   simple-scan doesn't scan from HP M1522nf (MFP), while xsane works
 * You can subscribe to bug 575191 by following this link: 
https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/575191/+subscribe

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

Title:
  no scanning result

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

[Bug 575191] Re: simple-scan doesn't scan from HP M1522nf (MFP), while xsane works

2010-12-09 Thread Valentijn Sessink

Same problem in Maverick with a HP LaserJet M2727nf MFP.  The last lines
of ltrace scanimage 21 | grep sane_ read:

sane_start(0x84ec568, 0x804d7a0, 0, 0xbfc8bb54, 0) = 0
sane_get_parameters(0x84ec568, 0xbfc8bb24, 0, 0xbfc8bb54, 0) = 0
sane_read(0x84ec568, 0x851ad08, 32768, 0xbfc8bb50, 0) = 2
sane_strstatus(2, 0x851ad08, 32768, 0xbfc8bb50, 0) = 0xeceb64
__fprintf_chk(0x2a7580, 1, 0x80500ed, 0xbfc8e89c, 0xeceb64scanimage: sane_read: 
Operation was cancelled
sane_cancel(0x84ec568, 1, 0x80500ed, 0xbfc8e89c, 0xeceb64) = 0
sane_close(0x84ec568, 1, 0, 1, 0x31f918) = 0x2a83c0
sane_exit(0x84ec568, 1, 0, 1, 0x31f918)  = 0

When using xsane, scanning works as expected.

However, this bug should not be against simple-scan, but against sane-
utils. And, in fact, it's there already: bug #408366

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

Title:
  simple-scan doesn't scan from HP M1522nf (MFP), while xsane works

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

[Bug 350936] Re: Should shut down domains on system shutdown

Hmm. If libvirt shuts down the virtual machines it monitors, then these
virtual machines will also be shut down when updating libvirt.

-- 
Should shut down domains on system shutdown
https://bugs.launchpad.net/bugs/350936
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to kvm in ubuntu.

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 350936] Re: Should shut down domains on system shutdown

The proposals in this report (mine, John Morrissey's) all have a pre-
stop shutdown of virtual machines in their Upstart conf-file.

When you update libvirt-bin, dpkg will stop libvirt-bin before
upgrading. As a result — if you have implemented the pre-stop shutdown —
your virtual machines will all stop.

-- 
Should shut down domains on system shutdown
https://bugs.launchpad.net/bugs/350936
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to kvm in ubuntu.

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 350936] Re: Should shut down domains on system shutdown

Hmm. If libvirt shuts down the virtual machines it monitors, then these
virtual machines will also be shut down when updating libvirt.

-- 
Should shut down domains on system shutdown
https://bugs.launchpad.net/bugs/350936
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

[Bug 350936] Re: Should shut down domains on system shutdown