[Bug 1568459] Re: unison incompatible with older ubuntu/debian versions

[Paul Beardsell]

Problem is still present in 18.10

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

Title:
  unison incompatible with older ubuntu/debian versions

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

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

[Bug 1568459] Re: unison incompatible with older ubuntu/debian versions

[Paul Beardsell]

I confirm Todd Taft's report - this is still an issue in 18.04. The
whole purpose of having Unison as a Debian/Ubuntu package is to provide
the function that Unison is meant for - to allow syncing of files across
not only multiple machines, but multiple versions of an o/s and between
versions of o/s, current and old. This is not the case with Unison on
Ubuntu. It's the death of Unison - eventually - if unison-all does not
include support for unison as installed on heterogenous and old
hardware, other o/s.

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

Title:
  unison incompatible with older ubuntu/debian versions

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

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

[Bug 1764726] Re: logrotate duplicate processing incorrect

[Paul Beardsell]

** Description changed:

- A file which matches two different patterns in the logrotate.conf file causes 
a
- "duplicate log entry" error. The file is rotated but no other subsequent 
files are rotated.
+ logrotate 3.11.0
+ 
+ A file which matches two different patterns in the logrotate.conf file
+ causes a "duplicate log entry" error. The file is rotated but no other
+ subsequent files are rotated.
  
  This is illogical.
  (1) If a duplicate log entry is indeed an error then that file should not be 
rotated. It is.
  (2) Files to be rotated which are not in error should still be rotated. They 
are not.
  (3) [Small but important point:] The message is misleading - what is detected 
by logrotate is not a duplicate log entry but that a file matches more than one 
log entry. If no such duplicate +file+ exists the duplicate +log entry+ is not 
detected.
  
  Suggestions:
  (A) A duplicate should prevent processing of that file, but that file only.
  (B) A resolution hierarchy be specified so that [optionally - new directive?] 
which of the various duplicates should be used. Last [or first?] takes 
precedence.
  (C) Error message should be improved. Perhaps "file matches more than one 
pattern"
  
- Whatever, there is no easy workaround for the problem I describe here.
- For example: I wish to rotate all of many *.log files according to one
- rule except for special.log which I wish to rotate according to another
+ Whatever, there is no easy workaround for the problem I describe here. For 
example: I wish to rotate all of many *.log files according to one rule except 
for special.log which I wish to rotate according to another. This conf
+ file has the above described behaviour:
  
  *.log {
-   
+   
  }
  
  special.log {
-   
+   
  }
  
- has the above described behaviour. special.log is rotated, others are
- not. Yes, I have tested this, reversed the order, etc etc.
+ special.log is rotated, a "duplicate log entry" is reported, other
+ processing stops. Yes, I have tested this, reversed the order, etc etc.
+ If I take out the special.log stanza then the other files are
+ successfully rotated.

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

Title:
  logrotate duplicate processing incorrect

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

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

[Bug 1764726] [NEW] logrotate duplicate processing incorrect

[Paul Beardsell]

Public bug reported:

A file which matches two different patterns in the logrotate.conf file causes a
"duplicate log entry" error. The file is rotated but no other subsequent files 
are rotated.

This is illogical.
(1) If a duplicate log entry is indeed an error then that file should not be 
rotated. It is.
(2) Files to be rotated which are not in error should still be rotated. They 
are not.
(3) [Small but important point:] The message is misleading - what is detected 
by logrotate is not a duplicate log entry but that a file matches more than one 
log entry. If no such duplicate +file+ exists the duplicate +log entry+ is not 
detected.

Suggestions:
(A) A duplicate should prevent processing of that file, but that file only.
(B) A resolution hierarchy be specified so that [optionally - new directive?] 
which of the various duplicates should be used. Last [or first?] takes 
precedence.
(C) Error message should be improved. Perhaps "file matches more than one 
pattern"

Whatever, there is no easy workaround for the problem I describe here.
For example: I wish to rotate all of many *.log files according to one
rule except for special.log which I wish to rotate according to another

*.log {
  
}

special.log {
  
}

has the above described behaviour. special.log is rotated, others are
not. Yes, I have tested this, reversed the order, etc etc.

** Affects: logrotate (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/1764726

Title:
  logrotate duplicate processing incorrect

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

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

Re: [Bug 1568459] Re: unison incompatible with older ubuntu/debian versions

[Paul Beardsell]

Many Debian and Ubuntu versions e.g. Ubuntu Trusty don't have that version
available. Raspbian Wheezy neither. But those are just examples. Unison is
intended to allow for sync-ing of directories over multiple platforms,
Windows included. As a minimum 2.40 needs to be everywhere, but 2.32 would
also be useful.

p...@beardsell.com

On 5 February 2017 at 01:24, Mark Foster  wrote:

> How about just add the 2.48 version in {xenial,yakkety,zesty}-backports?
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1642079).
> https://bugs.launchpad.net/bugs/1568459
>
> Title:
>   unison incompatible with older ubuntu/debian versions
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/unison/+bug/
> 1568459/+subscriptions
>

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

Title:
  unison incompatible with older ubuntu/debian versions

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

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

[Bug 1642079] Re: more versions of unison package required to allow interoperability of all supported Ubuntu releases

[Paul Beardsell]

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

** Description changed:

  The unison package exists for only one reason - to allow a directory
  tree to be synchronised between different computers. But unison does not
  work unless similar versions are installed on both machines.
  
  In Ubuntu 16.04 and 16.20 only unison-2.48 is available but unison-2.40
  and earlier versions are in use on supported Ubuntu releases as well as
- on other Debian-based systems. Ubuntu is also available on many non-
+ on other Debian-based systems. Unison is also available on many non-
  Debian systems.
  
  The bug is that more unison versions need to be available on all
  currently supported Ubuntu releases. The Ubuntu package unison-all is
  meant to include all the necessary versions of unison but on 16.04 and
  16.10 only unison-2.48 is available. As a minimum unison-2.40 is
  required to be included in unison-all for 16.04 and 16.10.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unison (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Nov 15 23:12:18 2016
  InstallationDate: Installed on 2016-07-22 (116 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: unison
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  more versions of unison package required to allow interoperability of
  all supported Ubuntu releases

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

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

[Bug 1568459] Re: unison incompatible with older ubuntu/debian versions

[Paul Beardsell]

I confirm that installing the previous version from the dpkg works just
fine in 16.04 despite what is reported about incompatible ocaml
versions. I'm using unison to sync various debian-derived machines, some
on Ubuntu 14.04, some on 16.04 and some on various Debians and Raspbian
too.

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

Title:
  unison incompatible with older ubuntu/debian versions

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

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

[Bug 1568459] Re: unison incompatible with older ubuntu/debian versions

[Paul Beardsell]

This bug affects 16.10 also.

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

Title:
  unison incompatible with older ubuntu/debian versions

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

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

[Bug 1642079] [NEW] more versions of unison package required to allow interoperability of all supported Ubuntu releases

[Paul Beardsell]

Public bug reported:

The unison package exists for only one reason - to allow a directory
tree to be synchronised between different computers. But unison does not
work unless similar versions are installed on both machines.

In Ubuntu 16.04 and 16.20 only unison-2.48 is available but unison-2.40
and earlier versions are in use on supported Ubuntu releases as well as
on other Debian-based systems. Ubuntu is also available on many non-
Debian systems.

The bug is that more unison versions need to be available on all
currently supported Ubuntu releases. The Ubuntu package unison-all is
meant to include all the necessary versions of unison but on 16.04 and
16.10 only unison-2.48 is available. As a minimum unison-2.40 is
required to be included in unison-all for 16.04 and 16.10.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: unison (not installed)
ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
Uname: Linux 4.4.0-47-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Nov 15 23:12:18 2016
InstallationDate: Installed on 2016-07-22 (116 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
SourcePackage: unison
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

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

Title:
  more versions of unison package required to allow interoperability of
  all supported Ubuntu releases

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

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

[Bug 1547763] [NEW] gmediarender does not start as a service

[Paul Beardsell]

Public bug reported:

gmediarender does not start as a service unless files /etc/init.d/gmediarender 
and /etc/default/gmediarender are modified. 
Firstly the user nobody cannot be used because the process wants to write files.
And the audio params best left out. 
The whole service thing is a mess!

If you start the prog  from the command line as an ordniary user - zero
parms - it works!

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: gmediarender 0.0.7~git20150616-1
ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1
Uname: Linux 4.2.0-27-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Feb 20 03:43:27 2016
InstallationDate: Installed on 2015-09-04 (168 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
SourcePackage: gmrender-resurrect
UpgradeStatus: Upgraded to wily on 2015-10-23 (119 days ago)
mtime.conffile..etc.default.gmediarender: 2016-02-20T03:24:28.967651
mtime.conffile..etc.init.d.gmediarender: 2016-02-20T03:14:53.995083

** Affects: gmrender-resurrect (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug wily

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

Title:
  gmediarender does not start as a service

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gmrender-resurrect/+bug/1547763/+subscriptions

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

[Bug 1169920] [NEW] wrong date in desktop after suspend resume

[Paul Beardsell]

Public bug reported:

After resume the time is correct but when this is clicked on (top right)
yesterday's date is shown! I went into timedate settings and checked
that timedate are set to update via the internet. It was so configured.
I brought up a terminal window and the correct date was shown in
response to the date command. I went back into datetime settings and
unchecked and rechecked the update via the internet option. I logged off
from the desktop session and logged back in (no reboot) and all is
correct again. Annoying bug which almost caused me to miss an
appointment.

Description:Ubuntu 12.04.2 LTS
Release:12.04

Completely up to date, no strange repositories.

HP/Compaq 2510p

** Affects: ubuntu
 Importance: Undecided
 Status: New


** Tags: date desktop resume suspend unity

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

Title:
  wrong date in desktop after suspend resume

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

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

[Bug 1169920] Re: wrong date in desktop after suspend resume

[Paul Beardsell]

I have been prompted to identify the package against which to assign
this bug. I have no idea. I am running the std 12.04 desktop. The date
whuch was wrong is the one shown when I click on the time top-right.

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

Title:
  wrong date in desktop after suspend resume

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

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

[Bug 1165549] [NEW] virtualbox-dkms 4.1.12-dfsg-2ubuntu0.2: virtualbox kernel module failed to build

[Paul Beardsell]

Public bug reported:

Hmm. Tried to install virtualbox on Ubuntu 12.4.2 using 'apt-get install
virtualbox'. Did not work. HP2510P.

ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: virtualbox-dkms 4.1.12-dfsg-2ubuntu0.2
ProcVersionSignature: Ubuntu 3.5.0-26.42~precise1-generic 3.5.7.6
Uname: Linux 3.5.0-26-generic i686
ApportVersion: 2.0.1-0ubuntu17.1
Architecture: i386
DKMSKernelVersion: 3.5.0-26-generic
Date: Sat Apr  6 14:30:22 2013
InstallationMedia: Ubuntu 12.04.2 LTS Precise Pangolin - Release i386 
(20130213)
MarkForUpload: True
PackageArchitecture: all
PackageVersion: 4.1.12-dfsg-2ubuntu0.2
SourcePackage: virtualbox
Title: virtualbox-dkms 4.1.12-dfsg-2ubuntu0.2: virtualbox kernel module failed 
to build
UpgradeStatus: No upgrade log present (probably fresh install)
VirtualBox.ModInfo:

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


** Tags: apport-package i386 need-duplicate-check precise

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

Title:
  virtualbox-dkms 4.1.12-dfsg-2ubuntu0.2: virtualbox kernel module
  failed to build

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

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

[Bug 700801] Re: [GMail] cannot attach file

[Paul Beardsell]

Same versions etc, same problem.

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

Title:
  [GMail] cannot attach file

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

[Bug 689332] [NEW] editmoin will not login

[Paul Beardsell]

Public bug reported:

Binary package hint: editmoin

Please see https://bugs.launchpad.net/editmoin/+bug/689328

** Affects: editmoin (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/689332

Title:
  editmoin will not login 

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

[Bug 553237] Re: awk errors and invalid /etc/default/adjtimex

[Paul Beardsell]

This bug is not fixed. Upon install of adjtimex I experienced the awk
errors reported above by others. You can avoid seeing the awk errors if
you fix some BIOS flag, we're told. That's a *different* problem you've
fixed, that just suppresses the symptom. The awk error still exists.
adjtimex does not work out of the box. Currently the only easy
workaround to the awk error is to install karmic's version of the
package. Neither that nor the BIOS tinkering is for the ordinary Ubuntu
user. This bug still exists. Please re-open.

-- 
awk errors and invalid /etc/default/adjtimex
https://bugs.launchpad.net/bugs/553237
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 555761] Re: syntax error in /etc/default/adjtimex

[Paul Beardsell]

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

Savvas very helpfully provides a WORKAROUND which works on some systems,
not a solution. The solution is to fix the awk code. Preferably the
sanity check should not exist at all in adjtimex so the easiest is just
to REMOVE the unworking code rather than to fix it.  adjtimex is
supposed to work with really bad clocks. Bug still exists in Lucid.

-- 
syntax error in /etc/default/adjtimex
https://bugs.launchpad.net/bugs/555761
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 555761] Re: syntax error in /etc/default/adjtimex

[Paul Beardsell]

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

Or, better, in the interim, while a proper fix is awaited, please just
re-instate karmic's version 1.27 as the lucid version. That's the way to
make Debian GNU/Linux work for non-tech non-geeks. Isn't that the aim of
this whole Ubuntu thing?

-- 
syntax error in /etc/default/adjtimex
https://bugs.launchpad.net/bugs/555761
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

Re: [Bug 150690] Re: Can't drag a window to another workspace

[Paul Beardsell]

Closing this, marking it invalid, is inappropriate.  100 paper cuts
doesn't mean 100 trivial bugs which are easy to fix, it means 100 small
annoyances that piss off users, particularly newbie ones who don't know the
workarounds.  Please UNDO this change of status.

Paul Beardsell
p...@beardsell.com


On 17 August 2010 09:18, Vish vishubu...@gmail.com wrote:

 Closing papercut task as per Sebastien's comment.

 ** Changed in: hundredpapercuts
   Status: Triaged = Invalid

 --
 Can't drag a window to another workspace
 https://bugs.launchpad.net/bugs/150690
 You received this bug notification because you are a direct subscriber
 of the bug.


-- 
Can't drag a window to another workspace
https://bugs.launchpad.net/bugs/150690
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

Re: [Bug 150690] Re: Can't drag a window to another workspace

[Paul Beardsell]

The only available workaround: Disable compiz.  Compiz is but eye-candy, you
and your users will prefer Ubuntu with unbroken multiple workspaces.  And
candy isn't good for you :-)

Some would say that complaining about this bug means:
* you misunderstand the Ubuntu bug reporting politics
* you are ungrateful about others' hard work
* you do not understand how X11 ought to work
* you are mentally unstable and ought to switch to Windows XP

I'm now compiz free for 18 months.  One day at a time.

Paul Beardsell
p...@beardsell.com


On 14 June 2010 03:29, eats7 eats...@gmail.com wrote:

 Does anyone have a fix for lucid? This is ridiculous, after 3 years man,
 still nothing.

 --
 Can't drag a window to another workspace
 https://bugs.launchpad.net/bugs/150690
 You received this bug notification because you are a direct subscriber
 of the bug.


-- 
Can't drag a window to another workspace
https://bugs.launchpad.net/bugs/150690
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

Re: [Bug 150690] Re: Can't drag a window to another workspace

[Paul Beardsell]

I had not realised I was criticising you so very personally as to provoke
that outburst.

Perhaps it is you who misunderstand.  The current workaround for this bug is
to disable compiz.  But, one has to ask, and this is my point:  Why should
compiz even have the opportunity of breaking workspaces?  Were the
underlying design better then compiz would need to know *nothing* of
workspaces.  A way, perhaps, to have a better design, would be to have the
workspace functionality built in at a more fundamental lower level within
Gnome etc.  Perhaps my suggestion is flawed, perhaps not, BUT either way:
that compiz breaks this aspect of workspace functionality shows something is
wrong - something is too closely coupled to something else.

And, whatever you say, it would be very neat to have the various workspaces
addressable as :0.0, :0.1, :0.2 etc etc  This suggestion would not break the
thin client functionality to which you allude.

Paul Beardsell


On 24 May 2010 10:09, Oded Arbel o...@geek.co.il wrote:

 On Sun, 2010-05-23 at 17:17 +, Paul Beardsell wrote:
  If I wanted
  an app's display to open on a particular workspace on a monitor I could
 do
  so by specifying '-display :0.3' or to choose a particular monitor I
  could use '-display  :3'.  We miss a trick or two now.  And whereas
  implmentation details are left unspecified the intention is clear.  Where
  and when do we get the opportunity to use anything other than :0.0 on a
  modern Linux box, now?

 I would like you to know that multiple X servers on a single box are
 used heavily in enterprise and academic installations to run thin X
 clients, and multi-screen X servers (not Xinerama) are used to provide
 multiple consoles on a single desktop computer in many educational
 installations as well as a few home installations I've seen.

 Please don't knock off existing functionality just because you don't
 understand what it is used for - it is often there to provide for a
 legitimate need that cannot be satisfied otherwise, even if you have not
 personally have required it.

  If that was sorted then this bug would not exist in
  its current form i.e. with a workaround simply being to disable Compiz.

 I don't agree, and I think the implementation details for workspace
 management and paging should stay firmly inside a specific WM's
 implementation. I might be a good idea to specify a freedesktop.org API
 for pagers to talk to window managers, but if you've hardcoded in a spec
 how workspaces should be implemented then a lot of cool things like
 GNOME Shell's dynamic workspaces wouldn't happen (or be so much harder
 to implement).

 --
 Oded Arbel o...@geek.co.il

 --
 Can't drag a window to another workspace
 https://bugs.launchpad.net/bugs/150690
 You received this bug notification because you are a direct subscriber
 of the bug.


-- 
Can't drag a window to another workspace
https://bugs.launchpad.net/bugs/150690
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

Re: [Bug 150690] Re: Can't drag a window to another workspace

[Paul Beardsell]

In my opinion the whole workspace thing is a hack implemented against the
way X is supposed to work.  Each workspace is not traditionally addressable.
 E.g. I cannot choose which workspace/pane my windowed application opens in
- it's always the current one.  E.g both

xterm -display :0 
xterm -display :0.0 

open a window in the current workspace but

xterm -display :0.1 

fails with an error.  In my opinion

xterm -display :0 

should best open in the first (or, better, current) workspace on the current
X server

xterm -display :0.0 

should open in the 1st workspace and

xterm -display :0.1 

should open in the 2nd etc

Even if you fix the current problem the original hack remains.  Workspaces
should have been implemented differently.  Having said that I am very much
in favour of a fix to the hack rather than the current situation.

Paul Beardsell
(another Paul)

On 23 May 2010 02:21, Ryan Beard lampwic...@yahoo.com wrote:

 Paul -  I had a similar prognosis.  My initial plan is to develop a
 universal workspace switcher - one that will query (and monitor) the
 window manager to determine the compositing engine, and then play along.
 I'm reading up on some of the compiz APIs now.  I'd really like to
 incorporate some additional GUI mechanisms while I'm at it.  For
 example, I think it would greatly enhance the functionality to have OS X
 Dock-like 'zoom-on-mouse-over' to allow for easier and more accurate
 selection/placement of windows within the applet.  I probably won't get
 started coding until Monday, but hopefully I can have something to play
 with next week.  This will be a bit of a learning experience for me, but
 I figure this is a good place to get introduced to linux development.

 -ryan

 On Sat, 2010-05-22 at 19:41 +, PaulReiber wrote:
  Ryan - here's my understanding of this issue.  I believe, at the heart
  of the issue is that Compiz handles virtual desktops quite differently
  than Metacity.
 
  Because of this, it fakes any apps using the Metacity virtual
  desktop API into thinking there's only one virtual desktop.  I'm not
  sure of the details of how it does this; review the thread on this bug
  for some leads (hopefully).
 
  I haven't reviewed any of the patches that've been identified, because
  they slipped my attention; I wasn't aware any coding work had been
  done by anyone to attempt to address this.  I believe the key to doing
  this right is to have the applet be compiz-aware, and use the proper
  API if it's running; it'll be interesting to see what the patches do.
 
  Looking forward to collaborating with you on a solution.
 
  Kind regards,
  -Paul Reiber
  Phone: (210)854-8253
  Email: p...@reiber.org
  Web: http://bit.ly/reiber
 
 
 
  On Sat, May 22, 2010 at 9:32 AM, Ryan Beard lampwic...@yahoo.com
 wrote:
   Thanks Paul.  I've downloaded the Grub development kit, and I'll be
   setting up conary today.  I'll let you how things go.
  
   -ryan
  
   On Fri, 2010-05-21 at 22:36 +, PaulReiber wrote:
   Ryan,
  
   If you're willing to dig/investigate, code, debug, and submit, I'm
   certainly willing to help.
  
   I've been programming/administering UNIX for ~30 years, Linux for ~15.
   My strengths are... well, pretty wide-reaching, but not so much in the
   GUI/Gnome/Window-manager/Virtual-Desktop coding details, or I would
   have fixed this myself a long time ago.
  
   Let me know if/when you get stuck and I'll do my best to get you
   un-stuck.  Contact me off-list at p...@reiber.org any time.
  
   Kind regards,
   -Paul Reiber
  
  
   On Fri, May 21, 2010 at 2:48 PM, Ryan Beard lampwic...@yahoo.com
 wrote:
Paul -
   
I'm actually referring to the patch attached to this bug (posted in
comment #34: betterpatch.diff).  It appears to target pager.c, but I
can't find that file in 10.04.
   
I haven't researched the Fedora patch yet, but I will look into
 that.
   
I'm new to Gnome, and linux in general (been an
OpenSuse/Kubuntu/LinuxMint user for the past year), but I actually
noticed this bug within the first 30 minutes after installation.
  I'd
like to help if at all possible (I was a heavy .net programmer, but
 I've
been living in Qt Creator for the last 6 months), but I figured I
 should
start with whatever work has already been accomplished - this patch,
 and
the alleged Fedora patch - and build from there.
   
Thanks for the help.
   
--
Can't drag a window to another workspace
https://bugs.launchpad.net/bugs/150690
You received this bug notification because you are a direct
 subscriber
of a duplicate bug.
   
  
  
   --
   Can't drag a window to another workspace
   https://bugs.launchpad.net/bugs/150690
   You received this bug notification because you are a direct subscriber
   of a duplicate bug.
  
 

 --
 Can't drag a window to another workspace
 https://bugs.launchpad.net/bugs/150690
 You received this bug notification because you are a direct subscriber
 of the bug

Re: [Bug 150690] Re: Can't drag a window to another workspace

[Paul Beardsell]

I'm not sure I would change hardly a word of my posting.  It seems to me the
multi-monitor Unix systems I was lucky enough to work on sometimes in the
1990's could have been implemented just as poorly as the multi-workspace
idea we have in Gnome and similar on Linux.  But they were not.  If I wanted
an app's display to open on a particular workspace on a monitor I could do
so by specifying '-display :0.3' or to choose a particular monitor I
could use '-display  :3'.  We miss a trick or two now.  And whereas
implmentation details are left unspecified the intention is clear.  Where
and when do we get the opportunity to use anything other than :0.0 on a
modern Linux box, now?   If that was sorted then this bug would not exist in
its current form i.e. with a workaround simply being to disable Compiz.

Paul Beardsell
p...@beardsell.com


On 23 May 2010 18:41, Oded Arbel o...@geek.co.il wrote:

 Paul Beardsell  wrote:
  In my opinion the whole workspace thing is a hack implemented against the
  way X is supposed to work. Each workspace is not traditionally
 addressable.
   E.g. I cannot choose which workspace/pane my windowed application opens
 in
 ...
  fails with an error. In my opinion
 
  xterm -display :0 
 
  should best open in the first (or, better, current) workspace on the
 current
  X server
 
  xterm -display :0.0 
 
  should open in the 1st workspace and
 
  xterm -display :0.1 
 
  should open in the 2nd etc

 I think you have a misunderstanding of how the display parameter works -
 from 'man X':
 ---8---
 DISPLAY NAMES
   From the user's perspective, every X server has a display name of the
 form:

  hostname:displaynumber.screennumber
 ...
  screennumber
   Some  displays  share  their  input devices among two or more
 monitors.  These may be configured as a single logical screen, which allows
 windows to move across screens, or as individual screens, each with their
 own set of windows.  If configured such that each  monitor  has its  own
  set of windows, each screen is assigned a screen number (beginning at 0)
 when the X server for that display is started.  If the screen number is not
 given, screen 0 will be used.
 ---8---

 In a nutshell, X11 allows you to address a machine, then a server on
 that machine, then a specific logical screen on that server (for example
 when running with dual monitors and without Xinerama). Window managers
 add on top of that the notion of workspaces, but it was never something
 inherent in X. Granted different window manager implement workspaces in
 different and conflicting manners, but that is not because of some
 misuse of X semantics.

 Freedesktop.org's window manager spec (EWMH) has this to say about
 workspaces (
 http://standards.freedesktop.org/wm-spec/wm-spec-latest.html#id2552820):
 ---8---
 This spec assumes a desktop model that consists of one or more completely
 independent desktops which may or may not be larger than the screen area.
 When a desktop is larger than the screen it is left to the Window Manager if
 it will implement scrolling or paging.
 ...
 Window Managers that require / desire additional functionality beyond what
 can be achieved using the mechanisms set out in this specification may
 choose to implement their own pagers, which communicate with the Window
 Manager using further, window manager specific hints, or some other means.
 ---8---

 In a nutshell we don't know what to tell you, go ahead and do what you
 want. Oh well.

 --
 Can't drag a window to another workspace
 https://bugs.launchpad.net/bugs/150690
 You received this bug notification because you are a direct subscriber
 of the bug.


-- 
Can't drag a window to another workspace
https://bugs.launchpad.net/bugs/150690
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

Re: [Bug 150690] Re: Can't drag a window to another workspace

[Paul Beardsell]

Hear! Hear!

Paul Beardsell
p...@beardsell.com


On 9 April 2010 08:39, allankelly allanke...@gmail.com wrote:

 This is still present in 9.10. I believe the most important issues are
 those a) visible to new users out-of-the-box and b) which obviously
 differ from Windows. Hence this is a very important issue which is very
 likely to be noticed by new users, who will base their opinion of Ubuntu
 (and Linux) on first impressions.

 This discussion has been underway for 2.5 YEARS and from a user
 perspective NOTHING has happened.

 If the tooltip is removed or amended to say how to move windows between
 desktops then the new-user damage is removed.

 This is a serious reputational damage issue.

 Cheers, allan.

 --
 Can't drag a window to another workspace
 https://bugs.launchpad.net/bugs/150690
 You received this bug notification because you are a direct subscriber
 of the bug.


-- 
Can't drag a window to another workspace
https://bugs.launchpad.net/bugs/150690
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

Re: [Bug 150690] Re: Can't drag a window to another workspace

[Paul Beardsell]

Something is going wrong when my favourite o/s (of which I am a deeply
appreciative long time desktop user and boring evangelist) can have all its
window buttons moved top left and the background changed to lurid purple but
the desktop switcher does not work (for ordinary mortals) as it should.
 Still broken in 10.04.  Hyperbole?  I don't think so.

Paul Beardsell
p...@beardsell.com


On 9 April 2010 09:01, wdesmet krom...@gmail.com wrote:

 This only affects the workplace switcher applet, which I thought windows
 didn't have? You can still move windows between desktops using the
 option menu or the keyboard shortcut (ctr-alt-shift left/right). Or just
 dragging them to the edge of the screen.

 Not that I don't think it's important to fix something like this (a
 thousand paper cuts and all that), but there's no need for the
 hyperbole.

 --
 Can't drag a window to another workspace
 https://bugs.launchpad.net/bugs/150690
 You received this bug notification because you are a direct subscriber
 of the bug.


-- 
Can't drag a window to another workspace
https://bugs.launchpad.net/bugs/150690
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 517907] [NEW] ubuntuone-client stopped working a while back and still it's not

[Paul Beardsell]

Public bug reported:

Binary package hint: ubuntuone-client

Sorry to not be more helpful but ubuntu-one client will not connect.  I
have apt-get purged and re-installed.

ProblemType: Bug
.home.psb..config.ubuntuone.syncdaemon.conf:
 [bandwidth_throttling]
 read_limit = 65536
 write_limit = 65536
 on = True
.home.psb..config.ubuntuone.ubuntuone.client.conf:
 [ubuntuone]
 bookmarked = True
 connected = True
 connect = 0
 show_applet = 0
Architecture: i386
Date: Sat Feb  6 16:03:34 2010
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: wl
Package: ubuntuone-client 1.0.3-0ubuntu1
PackageArchitecture: all
ProcEnviron:
 PATH=(custom, user)
 LANG=en_GB.UTF-8
 SHELL=/bin/zsh
ProcVersionSignature: Ubuntu 2.6.31-16.53-generic
SourcePackage: ubuntuone-client
Tags:  ubuntu-unr
Uname: Linux 2.6.31-16-generic i686

** Affects: ubuntuone-client (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-bug i386 ubuntu-unr

-- 
ubuntuone-client stopped working a while back and still it's not
https://bugs.launchpad.net/bugs/517907
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 517907] Re: ubuntuone-client stopped working a while back and still it's not

[Paul Beardsell]

** Attachment added: .home.psb..cache.ubuntuone.log.oauth.login.log.txt
   
http://launchpadlibrarian.net/38815849/.home.psb..cache.ubuntuone.log.oauth.login.log.txt

** Attachment added: 
.home.psb..cache.ubuntuone.log.syncdaemon.exceptions.log.txt
   
http://launchpadlibrarian.net/38815850/.home.psb..cache.ubuntuone.log.syncdaemon.exceptions.log.txt

** Attachment added: Dependencies.txt
   http://launchpadlibrarian.net/38815851/Dependencies.txt

** Attachment added: UbuntuoneClientPackages.txt
   http://launchpadlibrarian.net/38815852/UbuntuoneClientPackages.txt

** Attachment added: XsessionErrors.txt
   http://launchpadlibrarian.net/38815853/XsessionErrors.txt

-- 
ubuntuone-client stopped working a while back and still it's not
https://bugs.launchpad.net/bugs/517907
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 517907] Re: ubuntuone-client stopped working a while back and still it's not

[Paul Beardsell]

OK, well now it *is* working.  I cleared the cache on my browser
(Chrome) and then I could see the files after login - unlike before.
And I stopped the client and restarted after a purge and re-install.
But no diagnostic messages!  Usability issues abound.

-- 
ubuntuone-client stopped working a while back and still it's not
https://bugs.launchpad.net/bugs/517907
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 439604] Re: boot process isn't paused while fsck runs on partition: boot process is completed with fsck running in the background preventing partition from mounting

[Paul Beardsell]

I don't like this feature and would like the system to WAIT for fsck to
finish.  bootwait should be the default for local disks.

-- 
boot process isn't paused while fsck runs on partition: boot process is 
completed with fsck running in the background preventing partition from mounting
https://bugs.launchpad.net/bugs/439604
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 59893] Re: changing to fcron removes ubuntu-desktop and autoremove wants to remove a lot of packages

[Paul Beardsell]

Fresh install of Ubuntu 9.10 - same problem. Still unfixed.

** Also affects: fcron (Ubuntu)
   Importance: Undecided
   Status: New

-- 
changing to fcron removes ubuntu-desktop and autoremove wants to remove a lot 
of packages
https://bugs.launchpad.net/bugs/59893
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 463201] Re: package dpkg 1.15.4ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Paul Beardsell]

Michael, too late! But there was nothing wrong with /var/log/dpkg.log as
far as I could tell.  I could edit it, for example.  I think the issue
is something to do with the machine being virtual. I have outstanding
queries with the providers.  And this upgrade was attemtped on the RC -
I will try again with the proper release of Karmic.  And I think I'll
try and mark this bug resolved ot cancelled or whatever, if I have the
perms for that. Paul

-- 
package dpkg 1.15.4ubuntu2 failed to install/upgrade: subprocess installed 
post-installation script returned error exit status 1
https://bugs.launchpad.net/bugs/463201
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 463201] Re: package dpkg 1.15.4ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Paul Beardsell]

Or do I change it to invalid?

-- 
package dpkg 1.15.4ubuntu2 failed to install/upgrade: subprocess installed 
post-installation script returned error exit status 1
https://bugs.launchpad.net/bugs/463201
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 459084] Re: Simple update incorrect on 2nd and subsequent rows of CSV file

[Paul Beardsell]

** Also affects: libsql-statement-perl (Debian)
   Importance: Undecided
   Status: New

-- 
Simple update incorrect on 2nd and subsequent rows of CSV file
https://bugs.launchpad.net/bugs/459084
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 463201] [NEW] package dpkg 1.15.4ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Paul Beardsell]

Public bug reported:

Binary package hint: dpkg

Upgrading from Ubuntu Jaunty server to final RC for Karmic.  Did not see
the error.  I'm just taking the default options here to get thru this
bug report.  Seemingly dpkg won't upgrade???  This is a std upgrade on a
vanilla Jaunty following the server upgrade instructions.

ProblemType: Package
Architecture: i386
DistroRelease: Ubuntu 9.10
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
Package: dpkg 1.15.4ubuntu2
SourcePackage: dpkg
Title: package dpkg 1.15.4ubuntu2 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
Uname: Linux 2.6.18-028stab059.6 i686

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


** Tags: apport-package i386

-- 
package dpkg 1.15.4ubuntu2 failed to install/upgrade: subprocess installed 
post-installation script returned error exit status 1
https://bugs.launchpad.net/bugs/463201
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 463201] Re: package dpkg 1.15.4ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Paul Beardsell]

** Attachment added: Dependencies.txt
   http://launchpadlibrarian.net/34592865/Dependencies.txt

** Attachment added: DpkgTerminalLog.gz
   http://launchpadlibrarian.net/34592866/DpkgTerminalLog.gz

-- 
package dpkg 1.15.4ubuntu2 failed to install/upgrade: subprocess installed 
post-installation script returned error exit status 1
https://bugs.launchpad.net/bugs/463201
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 463201] Re: package dpkg 1.15.4ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Paul Beardsell]

On running apt-get install the installation of dpkg is detected as incomplete 
and is continued.  Error message is 
touch: setting times of `/var/log/dpkg.log': Bad address

I have re-done apt-get update to have same error repeated upon another
apt-get install

Did the same with aptitude.  aptitude update then aptitude install
and here is the output:

sl2.mine.nu psb $ sudo aptitude install
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Reading extended state information   
Initializing package states... Done
The following NEW packages will be installed:
  smartmontools 
The following partially installed packages will be configured:
  dpkg 
0 packages upgraded, 1 newly installed, 0 to remove and 298 not upgraded.
Need to get 332kB of archives. After unpacking 823kB will be used.
Do you want to continue? [Y/n/?] 
Get:1 http://archive.ubuntu.com karmic/main smartmontools 5.38-3ubuntu2 [332kB]
Fetched 332kB in 0s (935kB/s) 
Setting up dpkg (1.15.4ubuntu2) ...
touch: setting times of `/var/log/dpkg.log': Bad address
dpkg: error processing dpkg (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 dpkg
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install.  Trying to recover:
Setting up dpkg (1.15.4ubuntu2) ...
touch: setting times of `/var/log/dpkg.log': Bad address
dpkg: error processing dpkg (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 dpkg
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Reading extended state information   
Initializing package states... Done

-- 
package dpkg 1.15.4ubuntu2 failed to install/upgrade: subprocess installed 
post-installation script returned error exit status 1
https://bugs.launchpad.net/bugs/463201
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 463201] Re: package dpkg 1.15.4ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Paul Beardsell]

file `/var/log/dpkg.log' was only writable by root so i chmod-ded 666
but and re-tried - no difference.

-- 
package dpkg 1.15.4ubuntu2 failed to install/upgrade: subprocess installed 
post-installation script returned error exit status 1
https://bugs.launchpad.net/bugs/463201
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 463201] Re: package dpkg 1.15.4ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Paul Beardsell]

There is something wrong with touch!

sl2 % sudo touch /var/log/dpkg.log
touch: setting times of `/var/log/dpkg.log': Bad address
sl2 % ls -l /var/log/dpkg.log  
-rw-rw-rw- 1 root adm 168272 Oct 29 11:51 /var/log/dpkg.log
sl2 % ls -ld /var/log 
drwxr-xr-x 10 root root 4096 Oct 29 04:57 /var/log
sl2 % ls -ld /var
drwxr-xr-x 15 root root 4096 Oct 29 10:10 /var

Trying to touch any file caused this error.  So I moved /bin/touch out
of the way, symbolically linked /bin/true to /bin/touch and tried again.
Now aptitude install completes the install of dpkg without error.

-- 
package dpkg 1.15.4ubuntu2 failed to install/upgrade: subprocess installed 
post-installation script returned error exit status 1
https://bugs.launchpad.net/bugs/463201
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 463201] Re: package dpkg 1.15.4ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Paul Beardsell]

But I cannot continue with upgrade:

sl2 % sudo apt-get dist-upgrade

gives:
E: Conf Broken insserv

As this is still a RC of Karmic I am trying to upgrade to I am going to
restore from backup image and try again this PM with proper release.

-- 
package dpkg 1.15.4ubuntu2 failed to install/upgrade: subprocess installed 
post-installation script returned error exit status 1
https://bugs.launchpad.net/bugs/463201
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 459084] Re: Simple update incorrect on 2nd and subsequent rows of CSV file

[Paul Beardsell]

I have reported this bug upstream to CPAN as it is not distro specific.
See https://rt.cpan.org/Public/Bug/Display.html?id=50788

** Bug watch added: CPAN RT #50788
   http://rt.cpan.org/Ticket/Display.html?id=50788

-- 
Simple update incorrect on 2nd and subsequent rows of CSV file
https://bugs.launchpad.net/bugs/459084
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 459084] Re: Simple update incorrect on 2nd and subsequent rows of CSV file

[Paul Beardsell]

** Attachment added: Gzipped tar of files to demonstrate bug in SQL::Statement 
1.15
   http://launchpadlibrarian.net/34250283/zupdate-bug.tar.gz

-- 
Simple update incorrect on 2nd and subsequent rows of CSV file
https://bugs.launchpad.net/bugs/459084
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 459084] [NEW] Simple update incorrect on 2nd and subsequent rows of CSV file

[Paul Beardsell]

Public bug reported:

Binary package hint: libsql-statement-perl

A simple update of a CSV delimited file incorrectly makes value of
column on 2nd and subsequent rows null.

sl2 % lsb_release -rd
Description:Ubuntu 9.04
Release:9.04
sl2 % 

sl2 % apt-cache policy libsql-statement-perl
libsql-statement-perl:
  Installed: 1.15-3
  Candidate: 1.15-3
  Version table:
 *** 1.15-3 0
500 http://archive.ubuntu.com jaunty/universe Packages
100 /var/lib/dpkg/status
sl2 % 

Attached is a compressed tar including a apport-cli file, the output of
apt-show-versions and the simplest code I could put together to
demonsrate the problem.  Unpack and make for instructions.  The
content of the zupdate.sh file is plainly understood.  Output from when
I run the test is included.

** Affects: libsql-statement-perl (Ubuntu)
 Importance: Undecided
 Status: New

-- 
Simple update incorrect on 2nd and subsequent rows of CSV file
https://bugs.launchpad.net/bugs/459084
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 459084] Re: Simple update incorrect on 2nd and subsequent rows of CSV file

[Paul Beardsell]

Bug is *not* evident in libsql-statement-perl 0.1020-2 Debian Woody.
Bug applies also to libsql-statement-perl 1.15-2 Ubuntu Hardy.

I suppose problem could perhaps be in another module such as libdbd-csv-
perl

-- 
Simple update incorrect on 2nd and subsequent rows of CSV file
https://bugs.launchpad.net/bugs/459084
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 150690] Re: Compiz Gutsy : Can't drag a window to another workspace

[Paul Beardsell]

I would like this fixed.  But (works for me) there is an acceptable
workaround:  Disable visual effects.  System - Preferences -
Appearance - Visual effects - None.  Then apps can be dragged
workspace to workspace in the workspace switcher app.

Paul Beardsell

-- 
Compiz Gutsy : Can't drag a window to another workspace
https://bugs.launchpad.net/bugs/150690
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