[Bug 1444427] Re: unstr always fails with "data file corrupted"

2022-04-10 Thread braoult
I proposed a patch here:
https://bugs.launchpad.net/ubuntu/+source/fortune-mod/+bug/1961954

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

Title:
  unstr always fails with "data file corrupted"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fortune-mod/+bug/127/+subscriptions


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

[Bug 1961954] Re: unstr (package fortune-mod) incorrectly reads data file

2022-02-23 Thread braoult
** Description changed:

- Hot to reproduce :
+ How to reproduce :
  
  $ strfile fort
  "fort.dat" created
  There were 36 strings
  Longest string: 201 bytes
  Shortest string: 25 bytes
  
  $ ls -l fort*
  -rw-rw-r-- 1 br br 3383 Feb 23 10:31 fort
  -rw-rw-r-- 1 br br  172 Feb 23 10:31 fort.dat
  
  $ unstr fort
  Input file: fort
  unstr: data file corrupted
  
  The bug is line 234 of unstr.c (source file:
  https://sources.debian.org/src/fortune-mod/1%3A1.99.1-7/util/unstr.c/).
  
  The current checked_fread() macro compares fread() return value with the 
number of bytes to read :
  #define checked_fread(item, size)  \
- if (fread(item, size, 1, Dataf) != size)   \
-   {\
- fprintf(stderr, "unstr: data file corrupted\n");   \
- exit(1);   \
-   }
+ if (fread(item, size, 1, Dataf) != size)   \
+   {\
+ fprintf(stderr, "unstr: data file corrupted\n");   \
+ exit(1);   \
+   }
  
  It should instead compare fread() return value with the number of items to 
read, which is 1 :
  #define checked_fread(item, size)  \
- if (fread(item, size, 1, Dataf) != 1)  \
-   {\
- fprintf(stderr, "unstr: data file corrupted\n");   \
- exit(1);   \
-   }
+ if (fread(item, size, 1, Dataf) != 1)  \
+   {\
+ fprintf(stderr, "unstr: data file corrupted\n");   \
+ exit(1);   \
+   }
  
  After changing the code, running the same commands give :
  $ strfile fort
  "fort.dat" created
  There were 36 strings
  Longest string: 201 bytes
  Shortest string: 25 bytes
  
  $ ls -l fort*
  -rw-rw-r-- 1 br br 3383 Feb 23 10:31 fort
  -rw-rw-r-- 1 br br  172 Feb 23 10:38 fort.dat
  
  $ ./unstr fort
  Input file: fort
  nothing to do -- table in file order

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

Title:
  unstr (package fortune-mod) incorrectly reads data file

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fortune-mod/+bug/1961954/+subscriptions


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

[Bug 1961954] [NEW] unstr (package fortune-mod) incorrectly reads data file

2022-02-23 Thread braoult
Public bug reported:

Hot to reproduce :

$ strfile fort
"fort.dat" created
There were 36 strings
Longest string: 201 bytes
Shortest string: 25 bytes

$ ls -l fort*
-rw-rw-r-- 1 br br 3383 Feb 23 10:31 fort
-rw-rw-r-- 1 br br  172 Feb 23 10:31 fort.dat

$ unstr fort
Input file: fort
unstr: data file corrupted

The bug is line 234 of unstr.c (source file:
https://sources.debian.org/src/fortune-mod/1%3A1.99.1-7/util/unstr.c/).

The current checked_fread() macro compares fread() return value with the number 
of bytes to read :
#define checked_fread(item, size)  \
if (fread(item, size, 1, Dataf) != size)   \
  {\
fprintf(stderr, "unstr: data file corrupted\n");   \
exit(1);   \
  }

It should instead compare fread() return value with the number of items to 
read, which is 1 :
#define checked_fread(item, size)  \
if (fread(item, size, 1, Dataf) != 1)  \
  {\
fprintf(stderr, "unstr: data file corrupted\n");   \
exit(1);   \
  }

After changing the code, running the same commands give :
$ strfile fort
"fort.dat" created
There were 36 strings
Longest string: 201 bytes
Shortest string: 25 bytes

$ ls -l fort*
-rw-rw-r-- 1 br br 3383 Feb 23 10:31 fort
-rw-rw-r-- 1 br br  172 Feb 23 10:38 fort.dat

$ ./unstr fort
Input file: fort
nothing to do -- table in file order

** Affects: fortune-mod (Ubuntu)
 Importance: Undecided
 Status: New

** Patch added: "unstr.c: fix fread() return value test"
   
https://bugs.launchpad.net/bugs/1961954/+attachment/5562975/+files/unstr.patch

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

Title:
  unstr (package fortune-mod) incorrectly reads data file

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fortune-mod/+bug/1961954/+subscriptions


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

[Bug 1880666] Re: Suspend does work only after half minute delay.

2020-06-21 Thread braoult
XUbuntu 20.04: In Screensaver Preferences, lock screen is disabled (in
fact when enabled it was a loop logging, impossible to unlock). However,
still locking (fortunately with no loop), don't know where this lock
comes from.

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

Title:
  Suspend does work only after half minute delay.

To manage notifications about this bug go to:
https://bugs.launchpad.net/xfce4-screensaver/+bug/1880666/+subscriptions

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

[Bug 1860931] [NEW] In screensaver preferences, Lock Screen tab, delay for lock screen cannot be edited

2020-01-26 Thread braoult
Public bug reported:

In screensaver preferences, Lock Screen tab:

For the "Lock Screen after the screensaver is active for" field, if we change 
the value with the "+/-" buttons, everything is fine.
However, if we change the value manually, and quit, when we come back, the old 
value is still there.

The only way to change the value is with the "+/-" buttons.

For me, either this should be fixed, or this field should not be
editable by hand.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: xfce4-screensaver 0.1.8-1
ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
Uname: Linux 5.3.0-26-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: XFCE
Date: Sun Jan 26 19:45:29 2020
SourcePackage: xfce4-screensaver
UpgradeStatus: Upgraded to eoan on 2019-12-19 (38 days ago)

** Affects: xfce4-screensaver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug eoan

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

Title:
  In screensaver preferences, Lock Screen tab, delay for lock screen
  cannot be edited

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xfce4-screensaver/+bug/1860931/+subscriptions

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

[Bug 1860637] [NEW] wrong usbview.desktop (Exec line)

2020-01-23 Thread braoult
Public bug reported:

The Exec line in /usr/share/applications/usbview.desktop is:

 Exec=su-to-root -X -c /usr/bin/usbview

There is no such su-to-root program.

br.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: usbview 2.0-21-g6fe2f4f-1ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
Uname: Linux 5.3.0-26-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: XFCE
Date: Wed Jan 22 18:20:14 2020
SourcePackage: usbview
UpgradeStatus: Upgraded to eoan on 2019-12-19 (34 days ago)

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


** Tags: amd64 apport-bug eoan usbview

** Attachment added: "A simple workaround until a better solution"
   
https://bugs.launchpad.net/bugs/1860637/+attachment/5322302/+files/usbview.desktop.patch

** Description changed:

  The Exec line in /usr/share/applications/usbview.desktop is:
  
-  Exec=su-to-root -X -c /usr/bin/usbview
+  Exec=su-to-root -X -c /usr/bin/usbview
  
- There is no such exec-to-root program.
+ There is no such su-to-root program.
  
  br.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: usbview 2.0-21-g6fe2f4f-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
  Uname: Linux 5.3.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Jan 22 18:20:14 2020
  SourcePackage: usbview
  UpgradeStatus: Upgraded to eoan on 2019-12-19 (34 days ago)

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

Title:
  wrong usbview.desktop (Exec line)

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

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

[Bug 1842174] [NEW] Emacs bug on version 26.1

2019-08-31 Thread braoult
Public bug reported:

Emacs is version 26.1 on Xubuntu 19.04. However, there is a bug for package 
management (https://debbugs.gnu.org/cgi/bugreport.cgi?bug=36873, 
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=36810, 
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=36725).
I think the bug is fixed in Emacs 26.2.90.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: emacs 1:26.1+1-3.2ubuntu2
ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18
Uname: Linux 5.0.0-25-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu27.1
Architecture: amd64
CurrentDesktop: XFCE
Date: Sat Aug 31 13:22:58 2019
InstallationDate: Installed on 2018-05-24 (463 days ago)
InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
PackageArchitecture: all
SourcePackage: emacs
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug disco

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

Title:
  Emacs bug on version 26.1

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

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

[Bug 1289977] Re: Ubuntu 14.04 Update breaks grub, resulting in error: symbol 'grub_term_highlight_color' not found

2014-05-01 Thread braoult
@psusi. You can add +1 to people having this issue. Don't say 1 million people 
have no problem,
if you don't speak about 14.04. Also, the 89 number is from prople who were 
able to boot.

My system is fresh 13.04, upgraded to 13.10, and 14.04.

I did not touch grub, and I was lucky enough to have a second computer (Apple) 
where I could
burn a boot-repair. What about others who just cannot, such as your mom? 
Silent, so no issue reported?

And no, I don't have dual boot. And yes I have 2 hard drives, but never
booted from the second one.

This is a serious bug, really. My computer would have been stoned without the 
Mac to help.
Another distro could be better, of course, if change management (especially 
testing) is correctly done.

I would add:  Also, once again, it can't be validated in an automatic way is 
a nonsence. A booting drive
(unique) can be validated. If the script is not sure, asking a question would 
not hurt.

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

Title:
  Ubuntu 14.04 Update breaks grub, resulting in error: symbol
  'grub_term_highlight_color' not found

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

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


[Bug 1247395] Re: qemu-launcher runs parameter:-kernel-kqemu. This should be -enable-kvm

2013-11-16 Thread braoult
A workaround, instead of editing /usr/bin/qemu-launcher is to (in Emulator tab):
- select Acceleration: Enable
- add --enable-kvm in Additional arguments

Tested on Saucy.

qemu-launcher 1.7.4-1ubuntu2
qemu 1.5.0+dfsg-3ubuntu5

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

Title:
  qemu-launcher runs parameter:-kernel-kqemu. This should be -enable-
  kvm

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu-launcher/+bug/1247395/+subscriptions

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


[Bug 494968] Re: package ntp 1:4.2.4p6+dfsg-1ubuntu5.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2009-12-17 Thread braoult
Hi Chuck,

Thanks, I don't get anymore the error after adding the group. However,
the user ntp does not belong to this group.

Regards,

Bruno.

-- 
package ntp 1:4.2.4p6+dfsg-1ubuntu5.1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
https://bugs.launchpad.net/bugs/494968
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ntp 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 494968] Re: package ntp 1:4.2.4p6+dfsg-1ubuntu5.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2009-12-17 Thread braoult
Hi Chuck,

Thanks, I don't get anymore the error after adding the group. However,
the user ntp does not belong to this group.

Regards,

Bruno.

-- 
package ntp 1:4.2.4p6+dfsg-1ubuntu5.1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
https://bugs.launchpad.net/bugs/494968
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 494968] [NEW] package ntp 1:4.2.4p6+dfsg-1ubuntu5.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2009-12-10 Thread braoult
Public bug reported:

Binary package hint: ntp

I am running Koala, and every time I make a package update (whatever
the package is), I get the following error:

   Setting up ntp (1:4.2.4p6+dfsg-1ubuntu5.1) ...
   chown: invalid group: `ntp:ntp'
   dpkg: error processing ntp (--configure):
   subprocess installed post-installation script returned error exit status 1

Interesting is:

   $ grep ntp /etc/passwd
   ntp:x:112:124::/home/ntp:/bin/false
   $ grep ntp /etc/group
   $ grep 124 /etc/group
   postdrop:x:124:

Group ntp does not exist. Could it be that the install script tried to create
this group with an already existing gid (postdrop)?

ProblemType: Package
Architecture: amd64
Date: Wed Dec  9 07:55:44 2009
DistroRelease: Ubuntu 9.10
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
NonfreeKernelModules: nvidia
Package: ntp 1:4.2.4p6+dfsg-1ubuntu5.1
ProcVersionSignature: Ubuntu 2.6.31-16.52-generic
SourcePackage: ntp
Title: package ntp 1:4.2.4p6+dfsg-1ubuntu5.1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
Uname: Linux 2.6.31-16-generic x86_64

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


** Tags: amd64 apport-package

-- 
package ntp 1:4.2.4p6+dfsg-1ubuntu5.1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
https://bugs.launchpad.net/bugs/494968
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ntp 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 494968] Re: package ntp 1:4.2.4p6+dfsg-1ubuntu5.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2009-12-10 Thread braoult

** Attachment added: AptOrdering.txt
   http://launchpadlibrarian.net/36654659/AptOrdering.txt

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

** Attachment added: Dmesg.txt
   http://launchpadlibrarian.net/36654662/Dmesg.txt

** Attachment added: DpkgTerminalLog.txt
   http://launchpadlibrarian.net/36654663/DpkgTerminalLog.txt

-- 
package ntp 1:4.2.4p6+dfsg-1ubuntu5.1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
https://bugs.launchpad.net/bugs/494968
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ntp 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 494968] [NEW] package ntp 1:4.2.4p6+dfsg-1ubuntu5.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2009-12-10 Thread braoult
Public bug reported:

Binary package hint: ntp

I am running Koala, and every time I make a package update (whatever
the package is), I get the following error:

   Setting up ntp (1:4.2.4p6+dfsg-1ubuntu5.1) ...
   chown: invalid group: `ntp:ntp'
   dpkg: error processing ntp (--configure):
   subprocess installed post-installation script returned error exit status 1

Interesting is:

   $ grep ntp /etc/passwd
   ntp:x:112:124::/home/ntp:/bin/false
   $ grep ntp /etc/group
   $ grep 124 /etc/group
   postdrop:x:124:

Group ntp does not exist. Could it be that the install script tried to create
this group with an already existing gid (postdrop)?

ProblemType: Package
Architecture: amd64
Date: Wed Dec  9 07:55:44 2009
DistroRelease: Ubuntu 9.10
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
NonfreeKernelModules: nvidia
Package: ntp 1:4.2.4p6+dfsg-1ubuntu5.1
ProcVersionSignature: Ubuntu 2.6.31-16.52-generic
SourcePackage: ntp
Title: package ntp 1:4.2.4p6+dfsg-1ubuntu5.1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
Uname: Linux 2.6.31-16-generic x86_64

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


** Tags: amd64 apport-package

-- 
package ntp 1:4.2.4p6+dfsg-1ubuntu5.1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
https://bugs.launchpad.net/bugs/494968
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 494968] Re: package ntp 1:4.2.4p6+dfsg-1ubuntu5.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2009-12-10 Thread braoult

** Attachment added: AptOrdering.txt
   http://launchpadlibrarian.net/36654659/AptOrdering.txt

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

** Attachment added: Dmesg.txt
   http://launchpadlibrarian.net/36654662/Dmesg.txt

** Attachment added: DpkgTerminalLog.txt
   http://launchpadlibrarian.net/36654663/DpkgTerminalLog.txt

-- 
package ntp 1:4.2.4p6+dfsg-1ubuntu5.1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
https://bugs.launchpad.net/bugs/494968
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