[Bug 1973093] [NEW] xmessage loses text area as buttons are added and -g
Public bug reported: xmessage text gets obscured with option combinations using buttons and geometry specifications. Quick background: xmessage creates a new grey window with a white text box inside it. Without -buttons, the white text box usually spans the full width of the grey window that contains it, leaving no margins. Things start going wrong when you start specifying -buttons or -g (geometry), and text can end up being obscured. Problem #1: If the width of all the buttons you specify makes the grey window wider than the text, the white text box does not increase in width to match. You end up with an undesirable wide grey margin on the right side of the white text box. If you resize the window, making it less wide, the grey margin does not narrow; it moves in and covers and obscures the text, even though there is plenty of room for the text. Suggested Fix #1: The white text box must always be created the same width as the window that contains it, with no useless grey margin to the right. Narrowing the width of the window should not cause text to be obscured by a wide and useless fixed grey margin. Reproduce: xmessage -buttons 1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20 "123456789" Problem #2: If you add a -g (geometry) option and specify just the width (not the height) for a window with buttons wider than the text box, the obscuring grey margin persists. If you add a "-g NNN" option, where NNN is the width that xmessage would have chosen itself, then you get exactly the same unpleasant behaviour as Problem #1 above. If you increase the NNN to be wider that what xmessage would have used, then both the window and the text box width are created increased by that amount, as if you had resized the window with a mouse. The useless grey margin to the right of the text box stays the same width, just as in Problem #1. If you decrease the NNN to be narrower that what xmessage would have used, then both the window and the text box width are created decreased by that amount, as if you had resized the window with a mouse. Not all buttons will show; this is expected. What is not expected is that the useless grey margin to the right of the text box stays the same width, and so it now overwrites and obscures the text, even though there is plenty of room for the text. If you resize the window back so that all the buttons show, all the text also shows and we're back to Problem #1 above. Suggested Fix #2: Same as above. Reproduce (width 541 is my xmessage chosen width for font "fixed"): xmessage -g 400 -buttons 1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20 "123456789" xmessage -g 541 -buttons 1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20 "123456789" xmessage -g 700 -buttons 1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20 "123456789" Problem #3: If you add a -g option and specify both the width *and* the height for a window with buttons wider than the text, things get much worse. If you add a "-g NNNx55" option, where NNN is the width that xmessage would have chosen itself and "55" is about the same height, you would expect to get exactly the same results as if you didn't specify any geometry at all. That's not what happens. You get a fixed-width text window about 12 characters wide, with a huge grey margin on the right. It doesn't matter what size text you specify; the white text box will be created about 12 characters wide and any text to the right of that will be masked and obscured by the wide grey margin. Changing the width of the window has all the problems of Problems #1 and #2 above. Suggested Fix #3: Same as above. Specifying a geometry that is identical to what xmessage would have chosen itself should create an identical window. Text should not be obscured. Reproduce (width 541 is my xmessage chosen width for font "fixed"): xmessage -g 541x55 -buttons 1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20 "123456789-123 YOU DON'T SEE THIS" ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: x11-utils 7.7+5build2 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed May 11 17:12:52 2022 DistUpgraded: 2022-04-04 16:21:26,723 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: v4l2loopback/0.12.5, 5.15.0-29-generic, x86_64: installed v4l2loopback/0.12.5, 5.15.0-30-generic, x86_64: installed GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Fujitsu Limited. 2nd Generation Core Processor Family Integrated Graphics Controller [10cf:15f5] InstallationDate: Installed on 2020-09-08 (610 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64
[Bug 1971750] Re: lsusb shows wrong/duplicate product name
This bug is fixed in the GIT repository at https://github.com/gregkh/usbutils -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971750 Title: lsusb shows wrong/duplicate product name To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usbutils/+bug/1971750/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971750] [NEW] lsusb shows wrong/duplicate product name
Public bug reported:
lsusb incorrectly labels a device using the product name from a previous
device.
In the listing below, the incorrect product name on the second 04d8:fee9
device ("Microsoft® LifeCam HD-5000") is a copy of the product name
of the first device in the list:
$ lsusub -s 3:
Bus 003 Device 002: ID 045e:076d Microsoft Corp. LifeCam HD-5000
Bus 003 Device 009: ID 090c:6300 Silicon Motion, Inc. - Taiwan (formerly
Feiya Technology Corp.) Kingston Reader
Bus 003 Device 007: ID 0451:8142 Texas Instruments, Inc. TUSB8041 4-Port Hub
Bus 003 Device 019: ID 04d8:fee9 Microchip Technology, Inc.
Bus 003 Device 011: ID 04d8:fee9 Microchip Technology, Inc. Microsoft®
LifeCam HD-5000
Bus 003 Device 006: ID 03eb:0902 Atmel Corp. 4-Port Hub
Bus 003 Device 013: ID 0bda:2838 Realtek Semiconductor Corp. RTL2838 DVB-T
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Device 04d8:fee9 is not a Microsoft device.
Below is a verbose listing of the device that displays the wrong product
name. You can see that "Microsoft" doesn't appear anywhere in the
verbose listing, except incorrectly on the title line. Perhaps lsusb is
forgetting to clear the product title string before listing each device,
so a device that is busy or doesn't report a string gets a previous
device's string?
$ lsusb -v -s 3:11
Bus 003 Device 011: ID 04d8:fee9 Microchip Technology, Inc. Microsoft®
LifeCam HD-5000
Device Descriptor:
bLength18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 255 Vendor Specific Class
bDeviceSubClass 0
bDeviceProtocol 255
bMaxPacketSize0 8
idVendor 0x04d8 Microchip Technology, Inc.
idProduct 0xfee9
bcdDevice1.00
iManufacturer 1 Clearly Open
iProduct2 PengAlert module
iSerial 3 1
bNumConfigurations 2
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 0x0012
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 4 Default
bmAttributes 0xc0
Self Powered
MaxPower0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber0
bAlternateSetting 0
bNumEndpoints 0
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass255 Vendor Specific Subclass
bInterfaceProtocol255 Vendor Specific Protocol
iInterface 4 (error)
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 0x0020
bNumInterfaces 1
bConfigurationValue 2
iConfiguration 5 (error)
bmAttributes 0xc0
Self Powered
MaxPower0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber0
bAlternateSetting 0
bNumEndpoints 0
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass255 Vendor Specific Subclass
bInterfaceProtocol255 Vendor Specific Protocol
iInterface 4 (error)
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 0x0020
bNumInterfaces 1
bConfigurationValue 2
iConfiguration 5 (error)
bmAttributes 0xc0
Self Powered
MaxPower0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass255 Vendor Specific Subclass
bInterfaceProtocol255 Vendor Specific Protocol
iInterface 5 (error)
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes2
Transfer TypeBulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes2
Transfer TypeBulk
Synch
[Bug 1967824] [NEW] using --reduce-factor disables --except
Public bug reported: This is a bug in both version `1.0.4` and version `1.0.5_master`. See https://github.com/firehol/iprange/issues/31 First, set up two test files: ~ $ catout $ iprange in --diff out 1.2.3.4/31 1.2.3.6 ~ Using any value of `--reduce-factor` causes the `--except` to be ignored: ~ $ iprange in --except except --reduce-factor 0 >out $ iprange in --diff out $ iprange in --except except --reduce-factor 10 >out $ iprange in --diff out $ iprange in --except except --reduce-factor 90 >out $ iprange in --diff out $ diff in out $ ~ ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: iprange 1.0.4+ds-2 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Apr 5 00:37:04 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2020-10-07 (544 days ago) InstallationMedia: Lubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: iprange UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: iprange (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967824 Title: using --reduce-factor disables --except To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iprange/+bug/1967824/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965076] Re: rsync --update incorrectly reports file "is newer" than itself
I am not arguing about the behaviour, which is correct and apparently hasn't changed. I'm complaining about the unannounced change in message from "is uptodate" to "is newer". Three problems: 1. The message "is newer" is an unannounced change from all previous versions of rsync that say "is uptodate". My scripts that look for "is newer" are all broken, because now every file is flagged as newer, even when the file is not newer. 2. I expect that a name flagged as "is newer" will be transferred when I remove the --update option, and that does not happen because the file is *NOT* newer; the message is wrong and no transfer happens. 3. The message changes with and without the --update option. If rsync says "is uptodate" without the --update option, why does that change to "is newer" when you add the option? Either the file is newer *OR* it is uptodate; it can't be both. Adding the --update option should not change "is uptodate" to "is newer". It is not newer; don't say it is. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965076 Title: rsync --update incorrectly reports file "is newer" than itself To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1965076/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965076] [NEW] rsync --update incorrectly reports file "is newer" than itself
Public bug reported: rsync 3.2.3 has a broken "--update" option.See the examples below. The "--update" option incorrectly makes rsync say a file is newer than itself. Remove the "--update" option, and rsync correctly says the file is "uptodate". The right output should of course be "is uptodate" in all cases. This bug also shows up between machines if the source rsync is 3.1.3 and the destination is 3.2.3. The bug does not show up if the source rsync is 3.2.3 and the destination is 3.1.3. $ touch foo $ rsync -avv --update foo . delta-transmission disabled for local transfer or --whole-file foo is newer <=== THIS IS NOT CORRECT - A file can't be newer than itself. total: matches=0 hash_hits=0 false_alarms=0 data=0 sent 38 bytes received 96 bytes 268.00 bytes/sec total size is 0 speedup is 0.00 $ rsync -avv foo . delta-transmission disabled for local transfer or --whole-file foo is uptodate <=== THIS IS CORRECT total: matches=0 hash_hits=0 false_alarms=0 data=0 sent 41 bytes received 106 bytes 294.00 bytes/sec total size is 0 speedup is 0.00 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: rsync 3.2.3-4ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Mar 15 22:47:44 2022 InstallationDate: Installed on 2022-03-16 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: rsync UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: rsync (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965076 Title: rsync --update incorrectly reports file "is newer" than itself To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1965076/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1804592] Re: usb usb2: We don't know the algorithms for LPM for this host, disabling LPM.
Description:Ubuntu 20.04.4 LTS Linux linux 5.13.0-35-generic #40~20.04.1-Ubuntu SMP Mon Mar 7 09:18:32 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Mar 11 10:43:28 linux kernel: [1.578010] usb usb6: We don't know the algorithms for LPM for this host, disabling LPM. Mar 11 10:43:28 linux kernel: [1.578061] usb usb6: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.13 Mar 11 10:43:28 linux kernel: [1.578066] usb usb6: New USB device strings: Mfr=3, Product=2, SerialNumber=1 Mar 11 10:43:28 linux kernel: [1.578070] usb usb6: Product: xHCI Host Controller Mar 11 10:43:28 linux kernel: [1.578074] usb usb6: Manufacturer: Linux 5.13.0-35-generic xhci-hcd Mar 11 10:43:28 linux kernel: [1.578077] usb usb6: SerialNumber: :08:00.0 Mar 11 10:43:28 linux kernel: [1.578207] hub 6-0:1.0: USB hub found Mar 11 10:43:28 linux kernel: [1.578223] hub 6-0:1.0: 4 ports detected -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1804592 Title: usb usb2: We don't know the algorithms for LPM for this host, disabling LPM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804592/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958005] [NEW] rsyslogd mishandles startswith_i against $programname
Public bug reported:
The rsyslog program mis-handles the "startswith_i" comparison when applied
to $programname. Details follow:
Put this file in /etc/rsyslog.d/10-idallen.conf (it precedes all other
files):
if ( $programname startswith 'foo' ) then {
/var/log/idallen-cron.log
stop
}
Restart rsyslog:
# /etc/init.d/rsyslog restart
Run these four tests:
$ logger -t 'test' "This is: test"
$ logger -t 'foo' "This is: foo"
$ logger -t 'FOO' "This is: FOO"
$ logger -t '/junk' "This is /junk"
Expected and correct result:
The file /var/log/syslog contains three lines (correct):
Jan 14 23:08:09 ubuntu20 test: This is: test
Jan 14 23:08:09 ubuntu20 FOO: This is: FOO
Jan 14 23:08:09 ubuntu20 /junk: This is /junk
The file /var/log/idallen-cron.log contains just one line (correct):
Jan 14 23:08:09 ubuntu20 foo: This is: foo
Now make this change: In the 10-idallen.conf file change "startswith"
to "startswith_i". Restart rsyslog. Run the four tests. Here are the
unexpected and incorrect results:
The file /var/log/syslog contains just one line (should be two):
Jan 14 23:08:09 ubuntu20 test: This is: test
The file /var/log/idallen-cron.log contains three lines (should be two):
Jan 14 23:08:09 ubuntu20 foo: This is: foo
Jan 14 23:08:09 ubuntu20 FOO: This is: FOO
Jan 14 23:08:09 ubuntu20 /junk: This is /junk <== SHOULD NOT BE HERE
The '/junk' line should *NOT* be matched using "startswith_i 'foo'".
The same bug happens using '[junk' as the tag. Any number of blanks
may precede the / or the [ character and still cause the bug.
$ logger -t ' /anything' "This also triggers the bug."
$ logger -t ' [anything' "This also triggers the bug."
The bug did not appear when matching against $syslogtag:
# This does not show the bug:
if ( $syslogtag startswith_i 'foo' ) then {
/var/log/idallen-cron.log
stop
}
I tried to use "startswith" and "startswith_i" to match against the
"$msg" instead of against "$programname" or "$syslogtag" but could not
get any match at all no matter what I used as my logger message text:
# This never matches anything:
if ( $msg startswith 'foo' ) then {
/var/log/idallen-cron.log
stop
}
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: rsyslog 8.2001.0-1ubuntu1.1
ProcVersionSignature: Ubuntu 5.11.0-46.51~20.04.1-generic 5.11.22
Uname: Linux 5.11.0-46-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
Date: Sat Jan 15 02:02:24 2022
EcryptfsInUse: Yes
InstallationDate: Installed on 2020-10-07 (464 days ago)
InstallationMedia: Lubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
SourcePackage: rsyslog
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.logrotate.d.rsyslog: [modified]
mtime.conffile..etc.logrotate.d.rsyslog: 2020-12-27T12:21:35.307395
** Affects: rsyslog (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug focal third-party-packages
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958005
Title:
rsyslogd mishandles startswith_i against $programname
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1958005/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1957863] [NEW] coding errors in update-motd-fsck-at-reboot script
Public bug reported: The script /usr/lib/update-notifier/update-motd-fsck-at-reboot contains some coding errors. One of the errors hides the other error: 1. It sets two variables NEEDS_FSCK_CHECK and NEED_FSCK_CHECK (missing 'S') but only checks one of them (NEEDS_FSCK_CHECK). Because of this error, the script doesn't always initialize the value of NEEDS_FSCK_CHECK at the start of the script, so whatever value might happen to be passed in from the environment of the script could force a check even if the script would not itself do so. Rename variable NEED_FSCK_CHECK to NEEDS_FSCK_CHECK and always run your Bourne shell scripts with the "-u" (check for undefined variables) option enabled: #!/bin/sh -u 2. It sets the variables with values "no" and "yes", but *any* value set in the variables means "yes". (It doesn't check that the value is actually "yes", so even "no" means "yes".) Because of coding error #1, this coding error #2 has no effect on the script operation, so if you fix coding error #1 without fixing this one, the script will incorrectly always run. You have to fix both. Change: if [ -n "$NEEDS_FSCK_CHECK" ]; then to actually check for a "yes": if [ "$NEEDS_FSCK_CHECK" = 'yes' ]; then P.S. This script uses dumpe2fs that waits for all the disks on your system to spin up, which can significantly delay an ssh login to your system, as well as cause unnecessary wear on all your normally idle disks since the script seems to run frequently. If you don't like this behaviour (and don't need the fsck information it generates), you can render the script inactive by adding this line to /etc/crontab: 01 * * * * root f=/var/lib/update-notifier/fsck-at-reboot ; test -e $f && touch $f It would be nice if there were a cleaner way (perhaps something in /etc/default/?) to disable all this disk-spin-up activity, but that would be a different bug report. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: update-notifier-common 3.192.30.10 ProcVersionSignature: Ubuntu 5.11.0-46.51~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Jan 13 23:40:37 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2020-10-07 (463 days ago) InstallationMedia: Lubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: update-notifier UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apt.apt.conf.d.10periodic: [modified] mtime.conffile..etc.apt.apt.conf.d.10periodic: 2020-10-08T05:49:47.646282 ** Affects: update-notifier (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1957863 Title: coding errors in update-motd-fsck-at-reboot script To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1957863/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942063] Re: /usr/man symlink breaks apropos man -k due to fsstnd
If you could at least document what "/fsstnd" is (when the mandb man page says FSSTND should use /var/catman not /fsstnd), and why /usr/man and /usr/share/man are different and must look in different places in the MANDB_MAP, then maybe the current behaviour wouldn't look like a bug but a feature. I don't know why /usr/man and /usr/share/man aren't exactly the same in the manpath.config file; any documentation help you can provide would make the current odd behaviour seem less odd. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942063 Title: /usr/man symlink breaks apropos man -k due to fsstnd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/man-db/+bug/1942063/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942063] [NEW] /usr/man symlink breaks apropos man -k due to fsstnd
Public bug reported: In the old days, man pages were stored under /usr/man. Now, they are stored under /usr/share/man. Ubuntu systems no longer have a /usr/man, so all our really old scripts and reflexes that look under /usr/man fail unless you think to add the helpful symlink "ln -s share/man /usr/man". But making that helpful symlink breaks "apropos" and "man -k" because in /etc/manpath.config are these two different locations for the "mandb" index database: MANDB_MAP /usr/man/var/cache/man/fsstnd MANDB_MAP /usr/share/man /var/cache/man If you add the symlink for /usr/man, then the index.db file created by "mandb" ends up under a sub-directory /var/cache/man/fsstnd where "apropos" and "man -k" can't find it. Of course you can add another helpful symlink "ln -s fsstnd/index.db /var/cache/index.db" to work-around the "apropos" problem, or you can set your "MANPATH=/usr/man", but surely it doesn't need to be a problem in the first place. 1. Please make "apropos" and "man -k" smarter. Either they could look in both /var/cache/man and /var/cache/man/fsstnd, or else "mandb" could resolve the symlink /usr/man to its absolute version /usr/share/man before looking it up in the manpath.config file and thus not create the unhelpful "/fsstnd" sub-directory that breaks "apropos". 2. The man page for "mandb" and the manpath.config file make no mention of the reason for the extra "/fsstnd" sub-directory. The manpath.config file says the "FHS compliant" index.db location should be /var/cache/man/index.db and the "FSSTND compliant" location is under /var/catman Either remove the mysterious "/fsstnd" or explain it. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: man-db 2.9.1-1 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Aug 30 04:37:46 2021 EcryptfsInUse: Yes InstallationDate: Installed on 2020-10-07 (326 days ago) InstallationMedia: Lubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: man-db UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: man-db (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942063 Title: /usr/man symlink breaks apropos man -k due to fsstnd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/man-db/+bug/1942063/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942056] [NEW] /etc/cron.monthly/acct fails if wtmp not rolled monthly
Public bug reported: The /etc/cron.monthly/acct cron script is run monthly by cron or anacron to "perform monthly login accounting" with the /var/log/wtmp file. The cron script only works correctly if the wtmp file is rolled exactly monthly and gives errors otherwise. Fixing the script to do monthly accounting on a wtmp file that is rolled on a schedule other than monthly is non-trivial, because as written, the cron script makes three invalid assumptions: 1. That accounting is rolled over exactly monthly. The actual number of days of account data being saved before rolling is settable by the local sysadmin. It could be any number of days, not only a month. If the number of days is shorter than a month, the cron script will lose data and incorrectly under-report the monthly login accounting. If the number of days is longer than a month, the cron script incorrectly looks for the data in the rolled file name wtmp.1 or wtmp.1.gz instead of in the actual wtmp file where it is still accumulating. 2. That the rolled accounting file is present as wtmp.1 or wtmp.1.gz If the number of days of account data being saved before rolling is longer than a month, then the file doesn't roll over on every month end and on a new system no rolled wtmp.1 or wtmp.1.gz file may exist when the cron script runs and an error is generated about the missing file: From: Anacron Subject: Anacron job 'cron.monthly' /etc/cron.monthly/acct: couldn't open file '': No such file or directory last: cannot open : No such file or directory The data is still accumulating in the /var/log/wtmp file and that is where the cron script must look. 3. That only one month of accounting data is in the wtmp.1 or wtmp.1.gz file. The cron script assumes that only one exact month of accounting data are saved in the rotated wtmp.1 or wtmp.1.gz file, because the cron script processes the whole rotated file with no date range. if log rolling is longer one month (e.g. one year), then the current month's accounting data will usually still be accumulating in the wtmp file, not in the wtmp.1 or wtmp.1.gz file, and if the wtmp.1 or wtmp.1.gz file exists it will contain more than a month worth of accounting (e.g. part or all of a year). A begin and end date must be used to extract just the current month, and the correct file name wtmp or wtmp.1 or wtmp.1.gz must be used to do it. Fixing the above three problems in the cron script is non-trivial because it will involve knowing the frequency of log rotation and then determining whether the current month of accounting data are in the wtmp, wtmp.1, or wtmp.1.gz files (or a combination, if log rolling is more frequent than monthly) and using date ranges to extract just the current month. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: acct 6.6.4-2 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Aug 29 18:15:12 2021 EcryptfsInUse: Yes InstallationDate: Installed on 2020-10-07 (326 days ago) InstallationMedia: Lubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: acct UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.default.acct: 2021-07-18T04:14:33.822817 ** Affects: acct (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942056 Title: /etc/cron.monthly/acct fails if wtmp not rolled monthly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acct/+bug/1942056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863390] Re: GPU lockup ring 0 stalled for more than X msec
I'm now getting radeon GPU lockup with the Ubuntu 5.11.0-25 and 5.11.0-27 kernels. The 5.8.0-63 kernel and all previous work fine. $ lspci | grep ATI 05:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV620 GL [FirePro 2450] 06:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] RV620 GL [FirePro 2450] I use three (of four possible) 1600x1200 LCD monitors on the four FirePro outputs. Selected lines from /var/log/syslog are attached. These are the actual repeating lockup lines: Aug 17 15:20:44 linux kernel: [ 7403.029720] radeon :06:00.0: GPU lockup (current fence id 0x0001 last fence id 0x0002 on ring 0) Aug 17 15:20:44 linux kernel: [ 7403.541687] radeon :06:00.0: ring 0 stalled for more than 11304msec The last two lines "GPU lockup" and "ring 0 stalled" repeat over and over. The keyboard and the X11 display won't respond. I can ssh into the machine, and I can type "reboot", but it hangs somewhere in the shutdown (or else it is waiting for something longer than I'm willing to wait). The system reboots when I type ALT-SYSRQ-B on the keyboard, and I select the 5.8.0-63 kernel and everything is fine. ** Attachment added: "Selected drm and radeon lines from syslog" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1863390/+attachment/5518846/+files/radeon.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863390 Title: GPU lockup ring 0 stalled for more than X msec To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1863390/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1937097] [NEW] atopacctd and atop break acct by moving pacct file
Public bug reported: The Debian people tell me this bug was fixed Upstream six months ago. Ubuntu 20.04 LTS systems have the atop/acct conflict problem where if you install acct it wants the pacct file in one place (/var/log/account/pacct) and then if you install atop it starts atopacctd that decides it should be in a different place (/run/pacct_source) and the two fight it out every time the accounting reloads, making a real mess. If you disable atopacctd to stop it from stealing the pacct file, then if you ever run atop as root, atop itself will steal the pacct file and start storing it in /var/cache/atop.d/atop.acct, because atop expects to find the pacct file under /var/account/pacct and that directory doesn't exist on Ubuntu, so atop thinks no accounting is in use and creates its own location, breaking the acct package again. Disabling atopacctd isn't sufficient. The Debian people tell me this bug was fixed Upstream six months ago. Please install the Debian fix. As a work-around on Ubuntu 20.04, I replaced /usr/sbin/atopacctd with a "sleep d" script that will prevent it from ever grabbing the accounting file (at least until the next atop package update), and I made a symlink so that atop finds the Ubuntu accounting file and doesn't itself grab the accounting file: # ln -s log/account /var/account Now atop and acct coexist on Ubuntu LTS, at least until the next package update. Reference: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=94 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: atop 2.4.0-3 [modified: usr/sbin/atopacctd] ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Jul 21 10:43:28 2021 EcryptfsInUse: Yes InstallationDate: Installed on 2020-10-07 (286 days ago) InstallationMedia: Lubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: atop UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: atop (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1937097 Title: atopacctd and atop break acct by moving pacct file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/atop/+bug/1937097/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1716186] Re: log retention time period should not be hardcoded
In Ubuntu 20.04 LTS the script /etc/init.d/atop calls /usr/share/atop/atop.daily which does read /etc/default/atop and uses the variable LOGGENERATIONS=28. Systemd /usr/local/lib/systemd/system/atop.service also calls /usr/share/atop/atop.daily. Confusingly, the file /etc/default/atop says not to use it: # /etc/default/atop # this file is no longer used and will be removed in a future release Someone who knows better needs to decide how and where these configurable numbers should be set and either use the /etc/default/atop file or remove the misleading comment. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1716186 Title: log retention time period should not be hardcoded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/atop/+bug/1716186/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1937091] [NEW] ts -r does not parse all perl Date::Parse formats
Public bug reported:
"ts -r" does not recognize three of the eleven example formats given in
the man page for Perl Date::Parse. In particular, it doesn't recognize
the standard ISO-8601 format "1995:01:24T09:08:17.1823213":
$ ts -r
1995:01:24T09:08:17.1823213
1995:01:24T09:08:17.1823213
1995-01-24T09:08:17.1823213
1995-01-24T09:08:17.1823213
1999 10:02:18 "GMT"
1999 10:02:18 "GMT"
$ man ts
...
If the -r switch is passed, it instead converts existing timestamps in
the input to relative times, such as "15m5s ago". Many common timestamp
formats are supported. Note that the Time::Duration and Date::Parse
perl modules are required for this mode to work.
$ man Date::Parse
...
EXAMPLE DATES
1995:01:24T09:08:17.1823213 ISO-8601
1995-01-24T09:08:17.1823213
...
1999 10:02:18 "GMT"
$ perl -w -e 'use Date::Parse; print str2time("1995:01:24T09:08:17.1823213"),
"\n";'
790956497.182321
$ perl -w -e 'use Date::Parse; print str2time("1995-01-24T09:08:17.1823213"),
"\n";'
790956497.182321
$ perl -w -e 'use Date::Parse; print str2time("1999 10:02:18 \"GMT\""),
"\n";'
932551338
"ts -r" also doesn't recognize other simple date formats that are
recognized by Date::Parse, e.g.
$ ts -r
2000/01/02 03:04
2000/01/02 03:04
2000-01-02 03:04
2000-01-02 03:04
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: moreutils 0.63-1
ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-59-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
CasperMD5CheckResult: skip
Date: Wed Jul 21 09:56:10 2021
EcryptfsInUse: Yes
InstallationDate: Installed on 2020-10-07 (286 days ago)
InstallationMedia: Lubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
SourcePackage: moreutils
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: moreutils (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug focal third-party-packages
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1937091
Title:
ts -r does not parse all perl Date::Parse formats
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/moreutils/+bug/1937091/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908025] [NEW] export var=~root does not expand ~root to /root
Public bug reported: Shouldn't these give the same results in dash, i.e. "/root"? They give the same output in bash. $ dash $ var=~root $ echo "$var" /root $ export var=~root $ echo "$var" ~root ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: dash 0.5.10.2-6 ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Dec 14 00:14:44 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2020-10-07 (67 days ago) InstallationMedia: Lubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: dash UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: dash (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908025 Title: export var=~root does not expand ~root to /root To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dash/+bug/1908025/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1586195] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1586195/+attachment/5327760/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1586195 Title: Realtek 8153-based ethernet adapter on usb3 eventually stops working requiring unplug/replug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1586195/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1586195] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1586195/+attachment/5327755/+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/1586195 Title: Realtek 8153-based ethernet adapter on usb3 eventually stops working requiring unplug/replug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1586195/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1586195] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1586195/+attachment/5327752/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1586195 Title: Realtek 8153-based ethernet adapter on usb3 eventually stops working requiring unplug/replug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1586195/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1586195] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1586195/+attachment/5327754/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1586195 Title: Realtek 8153-based ethernet adapter on usb3 eventually stops working requiring unplug/replug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1586195/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1586195] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1586195/+attachment/5327753/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1586195 Title: Realtek 8153-based ethernet adapter on usb3 eventually stops working requiring unplug/replug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1586195/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1586195] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1586195/+attachment/5327756/+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/1586195 Title: Realtek 8153-based ethernet adapter on usb3 eventually stops working requiring unplug/replug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1586195/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1586195] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1586195/+attachment/5327751/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1586195 Title: Realtek 8153-based ethernet adapter on usb3 eventually stops working requiring unplug/replug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1586195/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1586195] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1586195/+attachment/5327757/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1586195 Title: Realtek 8153-based ethernet adapter on usb3 eventually stops working requiring unplug/replug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1586195/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1586195] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1586195/+attachment/5327758/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1586195 Title: Realtek 8153-based ethernet adapter on usb3 eventually stops working requiring unplug/replug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1586195/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1586195] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1586195/+attachment/5327759/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1586195 Title: Realtek 8153-based ethernet adapter on usb3 eventually stops working requiring unplug/replug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1586195/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1586195] Re: Realtek 8153-based ethernet adapter on usb3 eventually stops working requiring unplug/replug
ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: idallen 30789 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2015-04-28 (1751 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 radeondrmfb 1 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-76-generic root=UUID=5a875d56-b2fd-43bd-b9a4-ecf90aced5fa ro ProcVersionSignature: Ubuntu 4.15.0-76.86-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-76-generic N/A linux-backports-modules-4.15.0-76-generic N/A linux-firmware 1.173.14 RfKill: Tags: bionic Uname: Linux 4.15.0-76-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-09-02 (528 days ago) UserGroups: adm audio cdrom davfs2 dip docker lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 06/10/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1303 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A79T Deluxe dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1303:bd06/10/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A79TDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Tags added: apport-collected bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1586195 Title: Realtek 8153-based ethernet adapter on usb3 eventually stops working requiring unplug/replug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1586195/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1586195] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1586195/+attachment/5327750/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1586195 Title: Realtek 8153-based ethernet adapter on usb3 eventually stops working requiring unplug/replug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1586195/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1586195] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1586195/+attachment/5327749/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1586195 Title: Realtek 8153-based ethernet adapter on usb3 eventually stops working requiring unplug/replug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1586195/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1586195] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1586195/+attachment/5327748/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1586195 Title: Realtek 8153-based ethernet adapter on usb3 eventually stops working requiring unplug/replug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1586195/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1586195] Re: Realtek 8153-based ethernet adapter on usb3 eventually stops working requiring unplug/replug
USB 3 Gigabit Ethernet device (Realtek) disconnect/reconnect repeats randomly. $ lsb_release -a [...] Description:Ubuntu 18.04.4 LTS $ uname -a Linux linux 4.15.0-76-generic #86-Ubuntu SMP Fri Jan 17 17:24:28 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux $ lsusb [...] Bus 009 Device 003: ID 0bda:8153 Realtek Semiconductor Corp. Bus 009 Device 054: ID 0bda:8153 Realtek Semiconductor Corp. Syslog (two incidents of many): Feb 10 05:38:56 idallen-oak kernel: [1148004.410285] r8152 9-3.4:1.0 eth3: Stop submitting intr, status -71 Feb 10 05:38:56 idallen-oak kernel: [1148004.578733] usb 9-3: USB disconnect, device number 39 Feb 10 05:38:56 idallen-oak kernel: [1148004.578741] usb 9-3.4: USB disconnect, device number 40 Feb 10 05:38:56 idallen-oak NetworkManager[1403]: [1581331136.8384] devices removed (path: /sys/devices/pci:00/:00:05.0/:05:00.0/usb9/9-3/9-3.4/9-3.4:1.0/net/eth3, iface: eth3) Feb 10 05:38:56 idallen-oak NetworkManager[1403]: [1581331136.8564] get unmanaged devices count: 2 Feb 10 05:38:56 idallen-oak kernel: [1148004.908306] usb 9-3: new SuperSpeed USB device number 41 using xhci_hcd Feb 10 05:38:56 idallen-oak kernel: [1148004.944551] usb 9-3: New USB device found, idVendor=0bda, idProduct=0411 Feb 10 05:38:56 idallen-oak kernel: [1148004.944558] usb 9-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Feb 10 05:38:56 idallen-oak kernel: [1148004.944563] usb 9-3: Product: 4-Port USB 3.0 Hub Feb 10 05:38:56 idallen-oak kernel: [1148004.944566] usb 9-3: Manufacturer: Generic Feb 10 05:38:57 idallen-oak kernel: [1148004.949495] hub 9-3:1.0: USB hub found Feb 10 05:38:57 idallen-oak kernel: [1148004.951169] hub 9-3:1.0: 4 ports detected Feb 10 05:38:57 idallen-oak upowerd[4883]: unhandled action 'bind' on /sys/devices/pci:00/:00:05.0/:05:00.0/usb9/9-3/9-3:1.0 Feb 10 05:38:57 idallen-oak upowerd[4883]: unhandled action 'bind' on /sys/devices/pci:00/:00:05.0/:05:00.0/usb9/9-3 Feb 10 05:38:57 idallen-oak kernel: [1148005.247277] usb 9-3.4: new SuperSpeed USB device number 42 using xhci_hcd Feb 10 05:38:57 idallen-oak kernel: [1148005.277094] usb 9-3.4: New USB device found, idVendor=0bda, idProduct=8153 Feb 10 05:38:57 idallen-oak kernel: [1148005.277102] usb 9-3.4: New USB device strings: Mfr=1, Product=2, SerialNumber=6 Feb 10 05:38:57 idallen-oak kernel: [1148005.277107] usb 9-3.4: Product: USB 10/100/1000 LAN Feb 10 05:38:57 idallen-oak kernel: [1148005.277111] usb 9-3.4: Manufacturer: CMI Feb 10 05:38:57 idallen-oak kernel: [1148005.277114] usb 9-3.4: SerialNumber: 01 Feb 10 05:38:57 idallen-oak kernel: [1148005.373123] usb 9-3.4: reset SuperSpeed USB device number 42 using xhci_hcd Feb 10 05:38:57 idallen-oak kernel: [1148005.752039] r8152 9-3.4:1.0 eth3: renamed from eth1 Feb 10 05:38:58 idallen-oak NetworkManager[1403]: [1581331138.2100] devices added (path: /sys/devices/pci:00/:00:05.0/:05:00.0/usb9/9-3/9-3.4/9-3.4:1.0/net/eth3, iface: eth3) Feb 10 05:39:00 idallen-oak kernel: [1148008.501102] r8152 9-3.4:1.0 eth3: carrier on A few minutes later, it repeats: Feb 10 10:56:43 idallen-oak kernel: [1167071.434329] r8152 9-3.4:1.0 eth3: Stop submitting intr, status -71 Feb 10 10:56:43 idallen-oak kernel: [1167071.597275] usb 9-3: USB disconnect, device number 41 Feb 10 10:56:43 idallen-oak kernel: [1167071.597283] usb 9-3.4: USB disconnect, device number 42 Feb 10 10:56:43 idallen-oak NetworkManager[1403]: [1581350203.5700] devices removed (path: /sys/devices/pci:00/:00:05.0/:05:00.0/usb9/9-3/9-3.4/9-3.4:1.0/net/eth3, iface: eth3) Feb 10 10:56:43 idallen-oak NetworkManager[1403]: [1581350203.5720] get unmanaged devices count: 2 Feb 10 10:56:43 idallen-oak kernel: [1167071.930010] usb 9-3: new SuperSpeed USB device number 43 using xhci_hcd Feb 10 10:56:43 idallen-oak kernel: [1167071.964334] usb 9-3: New USB device found, idVendor=0bda, idProduct=0411 Feb 10 10:56:43 idallen-oak kernel: [1167071.964341] usb 9-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Feb 10 10:56:43 idallen-oak kernel: [1167071.964346] usb 9-3: Product: 4-Port USB 3.0 Hub Feb 10 10:56:43 idallen-oak kernel: [1167071.964349] usb 9-3: Manufacturer: Generic Feb 10 10:56:43 idallen-oak kernel: [1167071.969105] hub 9-3:1.0: USB hub found Feb 10 10:56:43 idallen-oak kernel: [1167071.970389] hub 9-3:1.0: 4 ports detected Feb 10 10:56:43 idallen-oak upowerd[4883]: unhandled action 'bind' on /sys/devices/pci:00/:00:05.0/:05:00.0/usb9/9-3/9-3:1.0 Feb 10 10:56:43 idallen-oak upowerd[4883]: unhandled action 'bind' on /sys/devices/pci:00/:00:05.0/:05:00.0/usb9/9-3 Feb 10 10:56:44 idallen-oak kernel: [1167072.269853] usb 9-3.4: new SuperSpeed USB device number 44 using xhci_hcd Feb 10 10:56:44 idallen-oak kernel: [1167072.295017] usb 9-3.4: New USB device found, idVendor=0bda, idProduct=8153 Feb 10 10:56:44 idallen-oak kernel: [1167072.295025] usb 9-3.4: New USB device
[Bug 1432079] Re: Only works on left-most head or multi-head setup
** Attachment added: "Screen shot of drawing pen line from left-to-right showing error when pen crosses into right monitor" https://bugs.launchpad.net/ubuntu/+source/xournal/+bug/1432079/+attachment/4587015/+files/iwin.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1432079 Title: Only works on left-most head or multi-head setup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xournal/+bug/1432079/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1432079] Re: Only works on left-most head or multi-head setup
Yes, xournal 1:0.4.8-1 broken in Ubuntu 15.10 with two monitors joined using Xinerama. Input only works on the left monitor, not the right. If I put the xournal window straddling the two monitors and draw a pen free-form line from left-to-right, the line works fine on the left monitor but the instant the pen crosses into the right monitor, the line disconnects from the pen and zooms straight left off the left edge of the window and does not track the pen as it moves around on the right monitor. (Or perhaps it tracks the pen far off-screen to the left where I can't see it.) If I start a free-form pen line on the right monitor and move left, nothing is visible on the screen until the pen crosses into the left monitor, then a line suddenly appears from the far left across the screen to where the pen enters the left monitor, and then the line correctly tracks the pen as long as the pen stays on the left monitor. I can start typing text on the left monitor, and the text extends correctly onto the right monitor. I cannot start text on the right monitor; it isn't visible at all. I can start typing text on the left monitor, move the window over to the right monitor, and continue typing text (into the same place) just fine on the right monitor as long as I don't move the cursor out of the text box. I cannot move the window to the right monitor and then select anything, so I can't select any text boxes on the right monitor unless I move the window to the left monitor to select the box. Once selected, I can then move the window to the right monitor, but once the cursor leaves the text box on the right monitor, I can't re-select it. Definitely looks like a multi-monitor coordinate problem. ** Tags added: wily ** Description changed: There appearss to be a coordinate conversion problem with the latest code: the x-coordinate is negative when used on some screens... I've got a new multi-head bug I have not seen before... I've been casually using a 3-screen multi-head setup with xournal for about 4 - years, it's worked fine, until a recent upgrade to Ubunut 140.04/ linux + years, it's worked fine, until a recent upgrade to Ubunut 14.04/ linux mint rebecca. Currently Xournal only works on the left-most screen; nothing is drawn when used on the middle and right screens. However, data is saved: I do get a "save" prompt, and when saving, a file is generated. On loading the file, nothing is displayed. Looking at the file contents (after ungzipping) shows that the x-coordinate is negative(!) -- deleting the negative sign, and reloading the file does cause the artwork to display (although not in the correct location). Conclusion: something, somewhere is performing incorrect math on a multi-head setup. FWIW, it is a 3-head setup, and the rightmost heads is rotated, so the total display area is L-shaped, not rectangular. I have not seen this bug with other drawing programs. I did not see this bug with earlier versions (on ubuntu 12.04) ** Description changed: There appearss to be a coordinate conversion problem with the latest code: the x-coordinate is negative when used on some screens... I've got a new multi-head bug I have not seen before... I've been casually using a 3-screen multi-head setup with xournal for about 4 - years, it's worked fine, until a recent upgrade to Ubunut 14.04/ linux + years, it's worked fine, until a recent upgrade to Ubuntu 14.04/ linux mint rebecca. Currently Xournal only works on the left-most screen; nothing is drawn when used on the middle and right screens. However, data is saved: I do get a "save" prompt, and when saving, a file is generated. On loading the file, nothing is displayed. Looking at the file contents (after ungzipping) shows that the x-coordinate is negative(!) -- deleting the negative sign, and reloading the file does cause the artwork to display (although not in the correct location). Conclusion: something, somewhere is performing incorrect math on a multi-head setup. FWIW, it is a 3-head setup, and the rightmost heads is rotated, so the total display area is L-shaped, not rectangular. I have not seen this bug with other drawing programs. I did not see this bug with earlier versions (on ubuntu 12.04) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1432079 Title: Only works on left-most head or multi-head setup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xournal/+bug/1432079/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1002453] Re: Firefox Screen Freeze
This just started happening to me in Ubuntu 15.04 with Firefox 42.0, but only if I run Firefox under the old vtwm window manager: Firefox 42.0 "Mozilla Firefox for Ubuntu" canonical - 1.0 under Ubuntu 15.04. The browser now (in the past week or two) locks up when requested to enter Full Screen if not running under any window manager (or when running under an old window manager such as vtwm that doesn't have all the modern hooks). Reproduce: 1. Start up Ubuntu 15.04 with the full Unity desktop installed. 2. Clean out (remove or rename) $HOME/.mozilla to start clean. 3. Open Firefox. 4. Note that using F11 correctly resizes Firefox to Full Screen and back down. 5. Kill the window manager: run: initctl stop unity7 6. Return to Firefox and try F11 or turn on "Full Screen" from the menu. 7. Browser locks up. Changing tabs doesn't refresh the screen unless you do something to trigger an X11 refresh such as opening a menu. F11 does *not* undo the damage - the browser stays locked up. Using the Firefox menu to disable (un-check) "Full Screen" also does nothing. Nothing works. 8. Start an old window manager such as "vtwm". No change. Firefox is still locked up. 9. Exit vtwm. 10. Re-start the Unity window manager: run: initctl start unity7 11. Return to Firefox and use F11 or the menu "Full Screen" a few times and Firefox is working again. 12. Repeat as needed. ** Summary changed: - Firefox Screen Freeze + Firefox Screen Freeze in Full Screen mode -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1002453 Title: Firefox Screen Freeze in Full Screen mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1002453/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1516052] Re: [regression] 3.13.0-69 infinite ip rules
*** This bug is a duplicate of bug 1514785 *** https://bugs.launchpad.net/bugs/1514785 The recent Ubuntu 15.04 kernel update to vmlinuz-3.19.0-37-generic installed this same bug. I had to reboot back to vmlinuz-3.19.0-33-generic to avoid the loop. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1516052 Title: [regression] 3.13.0-69 infinite ip rules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1516052/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1514785] Re: kernel 3.16.0.52+53 - ip rule repeats all default rules (messing up rule table)
The recent Ubuntu 15.04 kernel update to vmlinuz-3.19.0-37-generic installed this same bug. I had to reboot back to vmlinuz-3.19.0-33-generic to avoid the loop. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1514785 Title: kernel 3.16.0.52+53 - ip rule repeats all default rules (messing up rule table) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1514785/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1045072] Re: bash generates spurious DEL on empty variable interpolation
This bug is gone in Ubuntu 12.04 using bash 4.2.25(1)-release ** Changed in: bash (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1045072 Title: bash generates spurious DEL on empty variable interpolation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1045072/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1281366] Re: ip command becomes slower with large number of network devices
Ubuntu 12.04.4 LTS 3.8.0-36-generic #52~precise1-Ubuntu SMP Mon Feb 3 21:54:46 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux I just said this bug affects me too, but what I really meant to say was the fix is broken for me too and shows if numbers instead of interface device names. I had to downgrade back to the previous version. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1281366 Title: ip command becomes slower with large number of network devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute/+bug/1281366/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 500822] Re: /init: line 7: can't open /dev/sr0: No medium found
Failure booting from USB using ubuntu-12.04.3-desktop-i386.iso on a Dell Inspiron 9300: - Repeated /init: line 7: can't open /dev/sr0: No medium found over and over - Error: Unable to find a medium containing a live file system - Drops into shell prompt: (initramfs) The USB was made with a direct dd onto the USB key: dd if=ubuntu-12.04.3-desktop-i386.iso of=/dev/sdb (Same errors happened with a USB key loaded using some other Windows USB creator utility.) Solution: - Use F6 to interrupt the boot. - Optional: remove the keywords quiet splash from the kernel line. - Add the keywords break debug to the kernel line and continue the boot. - Part way into the boot, it will drop to the (initramfs) prompt. - Doing ls -l /dev/sd* will show only sda devices - no sdb devices. - Wait a few minutes. Various messages will print. Keep waiting. - After a few minutes, doing ls -l /dev/sd* will show the USB key (sdb* devices). - Now, exit the shell and continue the boot. - It comes up fine. Seems to be a timing issue with getting the USB /dev/sdb* devices recognized right after boot. Adding the break and debug (probably only one of these is actually needed but I don't know which) slows down the process and waits long enough so that the USB device can be found by the kernel correctly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/500822 Title: /init: line 7: can't open /dev/sr0: No medium found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/500822/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1218998] [NEW] linux-lts-raring suggests installing non-existent packages
Public bug reported: Installing linux-image-3.8.0-29 into 12.04 suggests that I install other packages that do not exist: # apt-get install linux-image-3.8.0-29 fdutils linux-headers-3.8.0-29 Reading package lists... Done Building dependency tree Reading state information... Done Note, selecting 'linux-image-3.8.0-29-generic' for regex 'linux-image-3.8.0-29' Suggested packages: linux-lts-raring-doc-3.8.0 linux-lts-raring-source-3.8.0 linux-lts-raring-tools linux-headers-3.8.0-29-generic The following NEW packages will be installed: fdutils linux-headers-3.8.0-29 linux-image-3.8.0-29-generic 0 upgraded, 3 newly installed, 0 to remove and 0 not upgraded. Need to get 60.4 MB of archives. # apt-get install linux-lts-raring-doc-3.8.0 linux-lts-raring-tools Reading package lists... Done Building dependency tree Reading state information... Done Package linux-lts-raring-doc-3.8.0 is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source Package linux-lts-raring-tools is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source E: Package 'linux-lts-raring-doc-3.8.0' has no installation candidate E: Package 'linux-lts-raring-tools' has no installation candidate ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.8.0-29-generic 3.8.0-29.42~precise1 ProcVersionSignature: Ubuntu 3.5.0-39.60~precise1-generic 3.5.7.17 Uname: Linux 3.5.0-39-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.4 Architecture: amd64 Date: Fri Aug 30 12:08:53 2013 InstallationMedia: Ubuntu-Server 12.04.1 LTS Precise Pangolin - Release amd64 (20120817.3) MarkForUpload: True SourcePackage: linux-lts-raring UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-lts-raring (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1218998 Title: linux-lts-raring suggests installing non-existent packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-raring/+bug/1218998/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 227542] Re: man page for expect calls glob regular expression
Still an error in Ubuntu 12.04 man page. Yes, it's an upstream issue that Ubuntu should send upstream. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/227542 Title: man page for expect calls glob regular expression To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/expect/+bug/227542/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1045072] [NEW] bash generates spurious DEL on empty variable interpolation
Public bug reported:
#!/bin/bash -u
# BASH BUG: spurious DEL characters appear on empty variable interpolation.
# BASH 4.2.8(1)-release
# Script works fine (expected output) using /bin/dash.
# -Ian! D. Allen - idal...@idallen.ca - www.idallen.com
a=''
{
echo correct $a # correct empty output line
echo correct $a$a # correct empty output line
echo correct $a$a$a # correct empty output line
echo XwrongX $a$a$a$a # spurious two DEL chars appear at line end
echo correct a$a # correct single a on line
echo XwrongX a$a$a # spurious DEL char appears at line end
echo correct a$a$a# correct single a on line
echo correct a$a$a$a$a# correct single a on line
} | cat -v
ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: bash 4.2-0ubuntu3
ProcVersionSignature: Ubuntu 2.6.38-15.66-generic 2.6.38.8
Uname: Linux 2.6.38-15-generic x86_64
Architecture: amd64
Date: Sun Sep 2 15:36:55 2012
InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1)
SourcePackage: bash
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: bash (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug natty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1045072
Title:
bash generates spurious DEL on empty variable interpolation
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1045072/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1045072] Re: bash generates spurious DEL on empty variable interpolation
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1045072 Title: bash generates spurious DEL on empty variable interpolation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1045072/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 984574] Re: [network]: gnome-control-center crashed with SIGSEGV in refresh_ui()
** This bug is no longer a duplicate of bug 672930 Feature request for movie export menu: display zoom scale -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/984574 Title: [network]: gnome-control-center crashed with SIGSEGV in refresh_ui() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/984574/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 984574] Re: [network]: gnome-control-center crashed with SIGSEGV in refresh_ui()
Booted AMD x64 Desktop CD as Try Ubuntu on my desktop machine to see how it would handle my FireMV video card. No install done - I'm running the live CD. 8GB memory. Went to the Dash Home, typed n, selected Network. Selected All Settings. Selected Network. Died. Repeatable. Every time. I can open any number of other Settings entries, but I can't open Network twice. It always dies on the second try. Once, even opening another Settings icon also caused it to die (after starting with Network). I have one onboard 1G NIC, two PCI 100M NICs, one USB 1G NIC (that's four Wired entries). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/984574 Title: [network]: gnome-control-center crashed with SIGSEGV in refresh_ui() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/984574/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 906504] Re: corrupts fields with single leading digit followed by blank
From: Pekka Enberg penberg,at,kernel.org Subject: Re: xmlindent corrupts data Date: Tue, 24 Jan 2012 22:26:54 +0200 (EET) This is fixed in the newly created XML Indent repository: https://github.com/penberg/xmlindent I'll see if I can still figure out how to release and upload a new version to SourceForge... :-) Pekka -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/906504 Title: corrupts fields with single leading digit followed by blank To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xmlindent/+bug/906504/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 906504] Re: corrupts fields with single leading digit followed by blank
Pekka still hasn't uploaded a fix to SourceForge, and Ubuntu 12.04 still has the same bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/906504 Title: corrupts fields with single leading digit followed by blank To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xmlindent/+bug/906504/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 988045] Re: bash crashed with SIGSEGV in xmalloc()
** 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/988045 Title: bash crashed with SIGSEGV in internal_malloc() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/988045/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 906504] Re: corrupts fields with single leading digit followed by blank
** Attachment added: one-line XML file corrupted by xmlindent https://bugs.launchpad.net/bugs/906504/+attachment/2640205/+files/content.xml ** Attachment removed: one-line XML file corrupted by xmlindent https://bugs.launchpad.net/ubuntu/+source/xmlindent/+bug/906504/+attachment/2640205/+files/content.xml -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/906504 Title: corrupts fields with single leading digit followed by blank To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xmlindent/+bug/906504/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 906504] Re: corrupts fields with single leading digit followed by blank
** Attachment added: one-line XML file corrupted by xmlindent https://bugs.launchpad.net/ubuntu/+source/xmlindent/+bug/906504/+attachment/2640220/+files/content.xml -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/906504 Title: corrupts fields with single leading digit followed by blank To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xmlindent/+bug/906504/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 906504] [NEW] corrupts fields with single leading digit followed by blank
Public bug reported: Oneiric and Natty xmlindent version 0.2.17-2 on amd-64 This one-line XML file causes xmlindent to corrupt the first two fields 1 foo and 2 foo into 1foo and 2bar (removing the spaces). The field 23 okay is fine: table:table-celltext:p1 foo/text:p/table:table-cell/table :table-rowtable:table-row table:style-name=ro1table:table- celltext:p2 bar/text:p/table:table-cell/table:table-rowtable :table-row table:style-name=ro1table:table-celltext:p12 okay/text:p/table:table-cell/table:table-row/table:table Adding a newline between the first pair makes the bug go away for 1 foo, so the bug has something to do with it all being one line. I found the bug by doing this: Create a LibreOffice spreadsheet with three cells containing these strings (each cell containing one string containing one blank): 1 foo 2 bar 34 okay Save the document. Unzip the *.ods file and apply xmlindent to the content.xml file. The spaces after the digits 1 and 2 are gone, corrupting the fields into 1foo and 2bar. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: xmlindent 0.2.17-2 ProcVersionSignature: Ubuntu 2.6.38-13.53-generic 2.6.38.8 Uname: Linux 2.6.38-13-generic x86_64 Architecture: amd64 Date: Mon Dec 19 14:54:20 2011 InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1) SourcePackage: xmlindent UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xmlindent (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug natty oneiricl -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/906504 Title: corrupts fields with single leading digit followed by blank To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xmlindent/+bug/906504/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 855967] Re: vinagre crashed with SIGSEGV in g_type_check_instance_cast()
So vinaigre crashed (Ubuntu 11.04) and sent me through the bug reporting process, collecting 50MB of reporting information and uploading it all. Here in Launchpad, I was offered two similar crashes and asked if either matched mine. Of course one did, so I chose it. As far as I can tell, Launchpad then threw away all my uploaded crash report tracing info and simply added my name to the this affects me count. Now that I open up this bug, I see that it is Incomplete requiring a useful symbolic stack trace. For all I know, my crash had one, but Launchpad in its wisdom threw away my stack trace when it decided that my crash was similar to this one. Shouldn't Launchapd *always* upload the additional crash report info for developers to look at, rather than throwing it away, especially for bugs marked Incomplete - need stack trace? I have the dump sitting here at home if you want me to do something with it: 126 Oct 27 13:10 _usr_bin_vinagre.777.crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/855967 Title: vinagre crashed with SIGSEGV in g_type_check_instance_cast() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vinagre/+bug/855967/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 509180] Re: ecryptfs sometimes seems to add trailing garbage to encrypted files
See also my comments #104, #128, #129, #131, #132, #134, #141, 143. Ubuntu 11.10 Oneiric desktop new install, fully updated shows file corruption when reading ecryptfs files. Linux ubuntu 3.0.0-12-generic #20-Ubuntu SMP Fri Oct 7 14:56:25 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux Reading the same read-only 18GB ecryptfs file system I've been using above, I took md5sums of all the files and created a base file of 435,649 md5sum file entries. I ran a script that looped for every file in the base file. It copied each file to a tmp file, did an md5sum on the tmp file, and compared that md5sum with the saved md5sum in the base file. I ran three looped iterations of this script in parallel, each offset to start at a different third of the md5sum base file. On the third iteration, all three scripts found the same md5sum difference on the same file name: MD5MISMATCH at line 62461 d4015d1962291b00abff6d14d8e71bb6 639f9b2e0f6bce8b287b879a1b0e17b5 All three scripts, running separately, came up with the same incorrect md5sum for the tmp file copy, at three different times. The tmp copy was the same size as the original. Comparing the tmp file with the original: $ cmp -bl [original] [tmp] 4865 0 ^@ 110 H 4866 320 M-P 127 W 4867 314 M-L 254 M-, 4868 360 M-p 370 M-x 4869 3 ^C 147 g 4870 4 ^D73 ; 4871 360 M-p 237 M-^_ 4872 340 M-` 16 ^N 4873 60 0272 M-: 4875 0 ^@ 347 M-g 4876 0 ^@ 220 M-^P 4877 0 ^@36 ^^ 4878 0 ^@ 347 M-g 4879 240 M- 336 M-^ 4880 5 ^E 231 M-^Y 4896 157 o177 ^? On the next five subsequent passes by each of the three scripts, no md5sum changes were detected in any of the files, including the problem file identified above. The corruption is intermittent. From the kern.log file, here are some ecryptfs errors, but the errors below do *not* correspond to the time that the script found the md5sum difference (which was on 06:10am Oct 23): Oct 20 14:57:49 ubuntu kernel: [ 65.128562] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null) Oct 20 16:04:30 ubuntu kernel: [ 4066.054573] ecryptfs_decrypt_page: Error attempting to read lower page; rc = [-4] Oct 20 16:04:30 ubuntu kernel: [ 4066.054580] ecryptfs_readpage: Error decrypting page; rc = [-4] Oct 20 16:47:30 ubuntu kernel: [ 6645.362178] ecryptfs_decrypt_page: Error attempting to read lower page; rc = [-4] Oct 20 16:47:30 ubuntu kernel: [ 6645.362263] ecryptfs_readpage: Error decrypting page; rc = [-4] Oct 22 15:49:25 ubuntu kernel: [175960.571423] ecryptfs_decrypt_page: Error attempting to read lower page; rc = [-4] Oct 22 15:49:25 ubuntu kernel: [175960.571503] ecryptfs_readpage: Error decrypting page; rc = [-4] Oct 22 16:12:46 ubuntu kernel: [177361.428710] ecryptfs_decrypt_page: Error attempting to read lower page; rc = [-4] Oct 22 16:12:46 ubuntu kernel: [177361.428735] ecryptfs_readpage: Error decrypting page; rc = [-4] Oct 22 16:23:12 ubuntu kernel: [177987.700577] ecryptfs_decrypt_page: Error attempting to read lower page; rc = [-4] Oct 22 16:23:12 ubuntu kernel: [177987.700593] ecryptfs_readpage: Error decrypting page; rc = [-4] Oct 22 16:31:57 ubuntu kernel: [178512.471610] ecryptfs_decrypt_page: Error attempting to read lower page; rc = [-4] Oct 22 16:31:57 ubuntu kernel: [178512.471613] ecryptfs_readpage: Error decrypting page; rc = [-4] Oct 22 23:33:42 ubuntu kernel: [203817.735704] Valid eCryptfs headers not found in file header region or xattr region Oct 22 23:33:42 ubuntu kernel: [203817.735717] Either the lower file is not in a valid eCryptfs format, or the key could not be retrieved. Plaintext passthrough mode is not enabled; returning -EIO Oct 23 00:13:19 ubuntu kernel: [206194.602236] ecryptfs_decrypt_page: Error attempting to read lower page; rc = [-4] Oct 23 00:13:19 ubuntu kernel: [206194.602243] ecryptfs_readpage: Error decrypting page; rc = [-4] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/509180 Title: ecryptfs sometimes seems to add trailing garbage to encrypted files To manage notifications about this bug go to: https://bugs.launchpad.net/ecryptfs/+bug/509180/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 509180] Re: ecryptfs sometimes seems to add trailing garbage to encrypted files
See also my comments #104, #128, #129, #131, #132, #134, #141. The above ecryptfs corruption is reduced but not gone in Ubuntu 11.10 Oneiric: Linux ubuntu 3.0.0-12-generic #20-Ubuntu SMP Fri Oct 7 14:56:25 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux I repeatedly ran md5sum on a read-only ecryptfs partition with 18GB of files (many with multiple hard links) and the md5sum results *changed* on a few files on some of the runs. It took many more runs (several dozen) to discover the corruption than when using the 2.6.38 kernel, and *only* the md5sums changed between runs, not the file sizes as well as was true with 2.6.38. I also saw the corruption on files with only one link, where under 2.6.38 it seemed to happen only on files with more than one link. I'm running these tests using a VMware install of a fully-updated Ubuntu 11.10 Oneiric with a separate 32GB virtual disk containing the 18GB ecryptfs partition. I'm looping a full md5sum of all 18GB in one terminal window and in a second window I'm looping a simultaneous md5sum of a 4.2GB subdirectory. When corruption happens, both windows show it happening on the same file(s). Out of 48 runs over the full 18GB so far, four runs turned up files with different checksums. In the other loop, out of 171 runs over the 4.2GB subdirectory so far, 11 runs turned up files with different checksums. I did see some kern.log errors early in the testing process: Oct 20 14:57:49 ubuntu kernel: [ 65.128562] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null) Oct 20 16:04:30 ubuntu kernel: [ 4066.054573] ecryptfs_decrypt_page: Error attempting to read lower page; rc = [-4] Oct 20 16:04:30 ubuntu kernel: [ 4066.054580] ecryptfs_readpage: Error decrypting page; rc = [-4] Oct 20 16:47:30 ubuntu kernel: [ 6645.362178] ecryptfs_decrypt_page: Error attempting to read lower page; rc = [-4] Oct 20 16:47:30 ubuntu kernel: [ 6645.362263] ecryptfs_readpage: Error decrypting page; rc = [-4] Those errors all appeared long before the runs showing corruption. /dev/sdb1 on /mnt/sdb1 type ext4 (ro) /mnt/sdb1/idallen-ecryptfs/.Private on /home/idallen-ecryptfs type ecryptfs (ro,ecryptfs_unlink_sigs,ecryptfs_cipher=aes,ecryptfs_key_bytes=16,ecryptfs_sig=,ecryptfs_fnek_sig=) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/509180 Title: ecryptfs sometimes seems to add trailing garbage to encrypted files To manage notifications about this bug go to: https://bugs.launchpad.net/ecryptfs/+bug/509180/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 880120] [NEW] read -r does not protect backslashes
Public bug reported: Both natty and oneiric dash fail to protect backslashes when using read -r. natty: dash 0.5.5.1-7.2ubuntu1 oneiric: dash 0.5.5.1-7.4ubuntu1 Example bug: $ echo '000\n999' | dash -c ' read -r f ; echo $f ' 000 999 Other shells do it correctly: $ echo '000\n999' | bash -c ' read -r f ; echo $f ' 000\n999 $ echo '000\n999' | static-sh -c ' read -r f ; echo $f ' 000\n999 This means you can't use read to read arbitrary lines of text. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: dash 0.5.5.1-7.2ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-12.51-generic 2.6.38.8 Uname: Linux 2.6.38-12-generic x86_64 Architecture: amd64 Date: Sat Oct 22 18:28:32 2011 InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1) SourcePackage: dash UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: dash (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug natty oneiric -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/880120 Title: read -r does not protect backslashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dash/+bug/880120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 880120] Re: read -r does not protect backslashes
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/880120 Title: read -r does not protect backslashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dash/+bug/880120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 880120] Re: read -r does not protect backslashes
*** This bug is a duplicate of bug 259671 *** https://bugs.launchpad.net/bugs/259671 Thanks Jilles - you are absolutely right. I had forgotten about versions of echo that process backslashes. I see that one cannot turn off the backslash processing of the dash echo, which is why you need the printf. Thanks! ** Description changed: + Edit: This isn't a bug in read - it's the way dash's echo handles + backslashes. + Both natty and oneiric dash fail to protect backslashes when using read -r. natty: dash 0.5.5.1-7.2ubuntu1 oneiric: dash 0.5.5.1-7.4ubuntu1 Example bug: - $ echo '000\n999' | dash -c ' read -r f ; echo $f ' - 000 - 999 + $ echo '000\n999' | dash -c ' read -r f ; echo $f ' + 000 + 999 Other shells do it correctly: - $ echo '000\n999' | bash -c ' read -r f ; echo $f ' - 000\n999 + $ echo '000\n999' | bash -c ' read -r f ; echo $f ' + 000\n999 - $ echo '000\n999' | static-sh -c ' read -r f ; echo $f ' - 000\n999 + $ echo '000\n999' | static-sh -c ' read -r f ; echo $f ' + 000\n999 This means you can't use read to read arbitrary lines of text. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: dash 0.5.5.1-7.2ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-12.51-generic 2.6.38.8 Uname: Linux 2.6.38-12-generic x86_64 Architecture: amd64 Date: Sat Oct 22 18:28:32 2011 InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1) SourcePackage: dash 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/880120 Title: read -r does not protect backslashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dash/+bug/880120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 509180] Re: ecryptfs sometimes seems to add trailing garbage to encrypted files
See also comments #104, #128, #129, #131, #132, #134. Still seeing ecryptfs file size corruption (leading to file corruption) in latest Ubuntu 11.04 kernel update: Linux linux 2.6.38-12-generic #51-Ubuntu SMP Wed Sep 28 14:27:32 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux The ecryptfs occasionally returns the (larger) size of the underlying ecryptfs file, not the size of the decrypted file being accessed in the decrypted and mounted partition. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/509180 Title: ecryptfs sometimes seems to add trailing garbage to encrypted files To manage notifications about this bug go to: https://bugs.launchpad.net/ecryptfs/+bug/509180/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 550559] Re: hdd problems, failed command: READ FPDMA QUEUED
Ubuntu 11.04 natty
fresh boot - errors are during boot sequence
Linux linux 2.6.38-11-generic #50-Ubuntu SMP Mon Sep 12 21:17:25 UTC
2011 x86_64 x86_64 x86_64 GNU/Linux
# hdparm -i /dev/sdd
/dev/sdd:
Model=ST32000542AS, FwRev=CC37, SerialNo=5XW0S99F
Config={ HardSect NotMFM HdSw15uSec Fixed DTR10Mbs RotSpdTol.5% }
RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=4
BuffType=unknown, BuffSize=unknown, MaxMultSect=16, MultSect=off
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=3907029168
IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio1 pio2 pio3 pio4
DMA modes: mdma0 mdma1 mdma2
UDMA modes: udma0 udma1 udma2 udma3 udma4 udma5 *udma6
AdvancedPM=yes: unknown setting WriteCache=enabled
Drive conforms to: unknown: ATA/ATAPI-4,5,6,7
10-12 08:54:20 ata8: SATA max UDMA/133 abar m1024@0xfbafe400 port
0xfbafe780 irq 22
10-12 08:54:20 ata8: softreset failed (1st FIS failed)
10-12 08:54:20 ata8: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
10-12 08:54:20 ata8.15: Port Multiplier 1.1, 0x1095:0x5744 r33, 3 ports, feat
0x1/0x9
10-12 08:54:20 ata8.00: hard resetting link
10-12 08:54:20 ata8.00: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
10-12 08:54:20 ata8.01: hard resetting link
10-12 08:54:20 ata8.01: SATA link down (SStatus 0 SControl 320)
10-12 08:54:20 ata8.02: hard resetting link
10-12 08:54:20 ata8.02: SATA link down (SStatus 0 SControl 320)
10-12 08:54:20 ata8.00: ATA-8: ST32000542AS, CC37, max UDMA/133
10-12 08:54:20 ata8.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32)
10-12 08:54:20 ata8.00: configured for UDMA/133
10-12 08:54:20 ata8: EH complete
10-12 08:54:20 scsi 7:0:0:0: Direct-Access ATA ST32000542AS CC37 PQ: 0 ANSI: 5
10-12 08:54:20 sd 7:0:0:0: Attached scsi generic sg5 type 0
10-12 08:54:20 sd 7:0:0:0: [sdd] 3907029168 512-byte logical blocks: (2.00
TB/1.81 TiB)
10-12 08:54:20 sd 7:0:0:0: [sdd] Write Protect is off
10-12 08:54:20 sd 7:0:0:0: [sdd] Mode Sense: 00 3a 00 00
10-12 08:54:20 sd 7:0:0:0: [sdd] Write cache: enabled, read cache: enabled,
doesn't support DPO or FUA
10-12 08:54:20 sdd: sdd1
10-12 08:54:20 sd 7:0:0:0: [sdd] Attached SCSI disk
10-12 08:56:49 ata8.01: failed to read SCR 1 (Emask=0x40)
10-12 08:56:49 ata8.02: failed to read SCR 1 (Emask=0x40)
10-12 08:56:49 ata8.15: exception Emask 0x4 SAct 0x0 SErr 0x41 action 0x6
frozen
10-12 08:56:49 ata8.15: SError: { RecovData Handshk }
10-12 08:56:49 ata8.00: exception Emask 0x100 SAct 0x1f SErr 0x0 action 0x6
frozen
10-12 08:56:49 ata8.00: failed command: WRITE FPDMA QUEUED
10-12 08:56:49 ata8.00: cmd 61/00:00:00:b0:fc/04:00:01:00:00/40 tag 0 ncq
524288 out
10-12 08:56:49 res 40/00:10:00:b8:fc/00:00:01:00:00/40 Emask 0x4 (timeout)
10-12 08:56:49 ata8.00: status: { DRDY }
10-12 08:56:49 ata8.00: failed command: WRITE FPDMA QUEUED
10-12 08:56:49 ata8.00: cmd 61/00:08:00:b4:fc/04:00:01:00:00/40 tag 1 ncq
524288 out
10-12 08:56:49 res 40/00:10:00:b8:fc/00:00:01:00:00/40 Emask 0x4 (timeout)
10-12 08:56:49 ata8.00: status: { DRDY }
10-12 08:56:49 ata8.00: failed command: WRITE FPDMA QUEUED
10-12 08:56:49 ata8.00: cmd 61/00:10:00:b8:fc/04:00:01:00:00/40 tag 2 ncq
524288 out
10-12 08:56:49 res 40/00:10:00:b8:fc/00:00:01:00:00/40 Emask 0x4 (timeout)
10-12 08:56:49 ata8.00: status: { DRDY }
10-12 08:56:49 ata8.00: failed command: WRITE FPDMA QUEUED
10-12 08:56:49 ata8.00: cmd 61/00:18:00:bc:fc/04:00:01:00:00/40 tag 3 ncq
524288 out
10-12 08:56:49 res 40/00:10:00:b8:fc/00:00:01:00:00/40 Emask 0x4 (timeout)
10-12 08:56:49 ata8.00: status: { DRDY }
10-12 08:56:49 ata8.00: failed command: WRITE FPDMA QUEUED
10-12 08:56:49 ata8.00: cmd 61/00:20:00:c0:fc/04:00:01:00:00/40 tag 4 ncq
524288 out
10-12 08:56:49 res 40/00:10:00:b8:fc/00:00:01:00:00/40 Emask 0x4 (timeout)
10-12 08:56:49 ata8.00: status: { DRDY }
10-12 08:56:49 ata8.01: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6
frozen
10-12 08:56:49 ata8.02: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6
frozen
10-12 08:56:49 ata8.15: hard resetting link
10-12 08:56:59 ata8.15: softreset failed (1st FIS failed)
10-12 08:56:59 ata8.15: hard resetting link
10-12 08:57:05 ata8.15: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
10-12 08:57:05 ata8.00: hard resetting link
10-12 08:57:05 ata8.00: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
10-12 08:57:05 ata8.01: hard resetting link
10-12 08:57:06 ata8.01: SATA link down (SStatus 0 SControl 320)
10-12 08:57:06 ata8.02: hard resetting link
10-12 08:57:06 ata8.02: SATA link down (SStatus 0 SControl 320)
10-12 08:57:06 ata8.00: configured for UDMA/133
10-12 08:57:06 ata8.00: exception Emask 0x1 SAct 0x0 SErr 0x0 action 0x0 t4
10-12 08:57:06 ata8: EH complete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/550559
Title:
hdd problems, failed command: READ FPDMA QUEUED
To manage notifications about this bug go to:
[Bug 509180] Re: ecryptfs sometimes seems to add trailing garbage to encrypted files
Launchpad Janitor (janitor) wrote 18 hours ago: #133 This bug was fixed in the package linux - 2.6.32-34.77 It's broken in stock Ubuntu 11.04 using 2.6.38-11-generic #50-Ubuntu SMP Mon Sep 12 21:17:25 UTC 2011 x86_64. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/509180 Title: ecryptfs sometimes seems to add trailing garbage to encrypted files To manage notifications about this bug go to: https://bugs.launchpad.net/ecryptfs/+bug/509180/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 509180] Re: ecryptfs sometimes seems to add trailing garbage to encrypted files
Ubuntu 11.04 natty Linux ubuntu 2.6.38-11-generic #50-Ubuntu SMP Mon Sep 12 21:17:25 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux I'm now reproducing the problem in a VMware virtual machine by repeatedly md5sum scanning a subset of files on that 17GB directory as small as 119 MB. (If I scan too small a directory, some sort of caching seems to happen and I don't see any errors.) What is happening is that the sizes of some files are changing on some subsequent md5sum passes. Usually when one stat()s the file, one gets the actual size of the unencrypted file. Occasionally, the size of the underlying *encrypted* file is substituted for the real file size and so the md5sum sums some extra bytes that it shouldn't. It's tricky to get at the bad content of the file, since to do so I'd have to actually copy every file to a temporary location, check to see if the size of the copy matched the original, and complain if not. I'll work on doing that. Until then, here is an example. Here is the correct file, md5sum, and size (61440): 9a601197629e5c0b68ecad8d039d1b51 23 1575321 33056 2 777 777 0 61440 1316934939 1163069184 1316934615 4096 136 /home/idallen- ecryptfs/[filename] When I repeated the md5sum scanning over and over, suddenly I got this: a wrong md5sum and wrong file size (69632): e26ef8caef4c1eca7672a6e0678b3190 23 1575321 33056 2 777 777 0 69632 1316934939 1163069184 1316934615 4096 136 /home/idallen- ecryptfs/[filename] Where does 69632 come from? Well, look at the encrypted file size that corresponds to that inode: # find /mnt/sdb1/idallen-ecryptfs/.Private -inum 1575321 -ls 1575321 68 -r--r- 2 idallen idallen 69632 Nov 9 2006 /mnt/sdb1/idallen-ecryptfs/.Private/[...] There it is! The underlying *encrypted* file size is bleeding up to be the (incorrect) size of the *unencrypted* file on some passes. I'm also seeing these errors in kern.log, but these messages don't always appear when I'm seeing corruption, so I don't know how to relate them: [...] Sep 25 20:43:12 ubuntu kernel: [59348.543107] ecryptfs_decrypt_page: Error attempting to read lower page; rc = [-4] Sep 25 20:43:12 ubuntu kernel: [59348.543113] ecryptfs_readpage: Error decrypting page; rc = [-4] Sep 25 21:59:10 ubuntu kernel: [63906.460167] ecryptfs_read_and_validate_header_region: Error reading header region; rc = [-4] Sep 25 21:59:10 ubuntu kernel: [63906.460334] Valid eCryptfs headers not found in file header region or xattr region Sep 25 21:59:10 ubuntu kernel: [63906.460336] Either the lower file is not in a valid eCryptfs format, or the key could not be retrieved. Plaintext passthrough mode is not enabled; returning -EIO -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/509180 Title: ecryptfs sometimes seems to add trailing garbage to encrypted files To manage notifications about this bug go to: https://bugs.launchpad.net/ecryptfs/+bug/509180/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 509180] Re: ecryptfs sometimes seems to add trailing garbage to encrypted files
See also comments #104, #128, #129, #131. Corruption (file size incorrect for ecryptfs files) also happens with this kernel from ppa:kernel-ppa/pre-proposed : Linux ubuntu 2.6.38-11-generic #51~pre201109230902-Ubuntu SMP Fri Sep 23 09:15:48 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux dmesg shows: [ 245.530576] ecryptfs_decrypt_page: Error attempting to read lower page; rc = [-4] [ 245.530600] ecryptfs_readpage: Error decrypting page; rc = [-4] [ 245.531485] ecryptfs_decrypt_page: Error attempting to read lower page; rc = [-4] [ 245.531494] ecryptfs_readpage: Error decrypting page; rc = [-4] As noted previously, corruption of file sizes happens even when no errors show in dmesg or kern.log. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/509180 Title: ecryptfs sometimes seems to add trailing garbage to encrypted files To manage notifications about this bug go to: https://bugs.launchpad.net/ecryptfs/+bug/509180/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 509180] Re: ecryptfs sometimes seems to add trailing garbage to encrypted files
See also comments #104 and #128. In parallel with the looping md5sum of everything in the 17G ecryptfs read-only partition described above, I picked one of the files that had produced different md5sums on different runs and wrote this script to repeatedly md5sum the same file over and over (filename shortened for clarity): #!/bin/sh -u # -Ian! D. Allen - idal...@idallen.ca - www.idallen.com f=filename set -- $( md5sum $f ) start=$1 while : ; do set -- $( md5sum $f ) if [ $1 != $start ] ; then echo $start != $* fi done Over the course of two days running my tests, the above script produced two outputs, indicating two times when that one file was read and had a different checksum from when the script started: c68292cceb13f21de7375c46c0ffdf9a != 58a90406649b9e795f9e1e6b34b806f8 filename c68292cceb13f21de7375c46c0ffdf9a != 58a90406649b9e795f9e1e6b34b806f8 filename This file is on a read-only ecryptfs partition. The md5sum should not be changing. I note that when the md5sum does change, it always changes to the same other value; it's not random. In my tests, the ecryptfs corruption seems to happen only when reading from files with more than one link. The file itself is 1132 bytes. Its encrypted base file is 12288 bytes. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/509180 Title: ecryptfs sometimes seems to add trailing garbage to encrypted files To manage notifications about this bug go to: https://bugs.launchpad.net/ecryptfs/+bug/509180/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 858200] Re: atop crashed with SIGSEGV in __libc_start_main()
** 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/858200 Title: atop crashed with SIGSEGV in __libc_start_main() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/atop/+bug/858200/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 745836] Re: soffice.bin crashed with SIGSEGV in cppu::throwException()
1708372 33133 6 777 777 0 571 1316719634 889794256 1286771927 4096 24 9898979b1fd2290e0a84b7a61a948f69 25 2100112 33133 3 777 777 0 5171 1316719634 893955992 1286771928 4096 32 b0073486c0d777d08935c2de20555c1b 25 2100112 33133 3 777 777 0 5171 1316719634 893955992 1286771928 4096 32 2fa1ea39deb352b6ae6c299e247f6984 25 6432103 33056 2 777 777 0 10240 1316720038 1169747949 1286771772 4096 40 69ea53d5d395c2b66323908936bcab27 25 6432103 33056 2 777 777 0 10240 1316720038 1169747949 1286771772 4096 40 0102ddf40cc9970703be495364f6b49d 25 6553900 33200 2 777 777 0 21562 1316720038 1169144857 1286771772 4096 64 8dd8909086e374795bccdd0cdcaec708 25 6553900 33200 2 777 777 0 21562 1316720038 1169144857 1286771772 4096 64 2729fd22c4e2dc5c7dad55efea59816c 25 5259866 33188 2 777 777 0 11632 1316719638 1295994736 1306955878 4096 40 ef56472cf83a33203cdc9f75cfc96417 25 5259866 33188 2 777 777 0 11632 1316719638 1295994736 1306955878 4096 40 47383a0471b18b60a0927c4938a73590 25 5259896 33188 2 777 777 0 364 1316719638 1295994738 1306955879 4096 24 b58ce988f987e0f2b2cdea8d37f3ce5a 25 5259896 33188 2 777 777 0 364 1316719638 1295994738 1306955879 4096 24 765ab08d4bca476c9c2c2ae77c4de04d 25 4987811 33060 14 777 777 0 423 1316720053 947301176 1286771951 4096 24 9494a2f9c673ed2841bbb5f8dbe50078 25 4987811 33060 14 777 777 0 423 1316720053 947301176 1286771951 4096 24 5a8a9d71c274d5c89c73b15ca0b942b4 25 2100801 33133 5 777 777 0 1741 1316719634 893803806 1286771929 4096 24 8687150f675e9a3ff5a554b61a93bc46 25 2100801 33133 5 777 777 0 1741 1316719634 893803806 1286771929 4096 24 083e4d0879b8e6ff9fefba0a1e310ee1 25 1705547 33248 2 777 777 0 16282 1316719610 1037740744 1286771882 4096 48 99d7d3a3ccf7ae11159914a6f1d0733e 25 1705547 33248 2 777 777 0 16282 1316719610 1037740744 1286771882 4096 48 4131baafcda44afb321152863b7738ed 25 5124379 33188 10 777 777 0 1120 1316720061 966839592 1286771948 4096 24 41d163d06d9277abbe3b0a0241b12466 25 5124379 33188 10 777 777 0 1120 1316720061 966839592 1286771948 4096 24 3d9807caa06ecd0a5e7835fff35e59d6 25 4989066 33060 2 777 777 0 26693 1316720053 1095362037 1286771940 4096 72 aae1eb503271a48de565ae98b947bc93 25 4989066 33060 2 777 777 0 26693 1316720053 1095362037 1286771940 4096 72 110f8be7ab5a7dd7df6d92bcb3108870 25 5259894 33188 2 777 777 0 265 1316719638 1295994738 1306955876 4096 24 1dac22b20b7dd28dc474306f42f07bbb 25 5259894 33188 2 777 777 0 265 1316719638 1295994738 1306955876 4096 24 083e4d0879b8e6ff9fefba0a1e310ee1 25 1705547 33248 2 777 777 0 16282 1316719610 1037740744 1286771882 4096 48 476503e7893a0a65ac507fbc8cdf8fee 25 1705547 33248 2 777 777 0 16282 1316719610 1037740744 1286771882 4096 48 136ace18c7fe1a88a05e373fd2691509 25 2100812 33133 4 777 777 0 16775 1316719634 893803738 1286771929 4096 56 22a80a8aa3cb1ed7f861e6764ffd24b8 25 2100812 33133 4 777 777 0 16775 1316719634 893803738 1286771929 4096 56 4f8b2ae505831c13ababf97d88fb9c5b 25 6444861 33188 2 777 777 0 285 1316719548 1289288995 1289289103 4096 24 5ed806ab2c77de38da87c25f57704a59 25 6444861 33188 2 777 777 0 285 1316719548 1289288995 1289289103 4096 24 1e040e3e9f7cc9090fae3d96a5cd234d 25 1705492 33248 2 777 777 0 10889 1316719610 1037672622 1286771882 4096 40 fa4951d10c02ef6042135cce2c01189f 25 1705492 33248 2 777 777 0 10889 1316719610 1037672622 1286771882 4096 40 7fbb5e5a167f24bac8469606a5d0a26a 25 1705521 33248 2 777 777 0 12765 1316719610 1037715886 1286771882 4096 48 f909799efc770c7e5275cb2587627ade 25 1705521 33248 2 777 777 0 12765 1316719610 1037715886 1286771882 4096 48 7dfae954d7c6f4787d9236c989e2217f 25 1705492 33248 2 777 777 0 10889 1316719610 1037672622 1286771882 4096 40 fa4951d10c02ef6042135cce2c01189f 25 1705492 33248 2 777 777 0 10889 1316719610 1037672622 1286771882 4096 40 1010c5075017a665a9799aede68339ac 25 2100092 33133 8 777 777 0 2636 1316719634 891569196 1286771928 4096 24 55c4334ea6da9faf5a1d3c95c1103c3e 25 2100092 33133 8 777 777 0 2636 1316719634 891569196 1286771928 4096 24 3fb139d7a83c75b221da0f1cf6226207 25 2100807 33133 6 777 777 0 1642 1316719634 889568628 1286771929 4096 24 66af1020d4cec3603b158afe92492351 25 2100807 33133 6 777 777 0 1642 1316719634 889568628 1286771929 4096 24 6259773096a72272aae4ed28a6a362f1 25 6430577 33056 2 777 777 0 20480 1316720037 1175010335 1286771771 4096 56 dac8608422c39ab642eef0100e112053 25 6430577 33056 2 777 777 0 20480 1316720037 1175010335 1286771771 4096 56 ea01946c5d66c28f3471bfc286bda3a7 25 5124374 33188 5 777 777 0 1205 1316720061 966839592 1286771948 4096 24 ea62a726ee2b908cf45086f235c2a727 25 5124374 33188 5 777 777 0 1205 1316720061 966839592 1286771948 4096 24 -- | Ian! D. Allen - idal...@idallen.ca - Ottawa, Ontario, Canada | Home Page: http://idallen.com/ Contact Improv: http://contactimprov.ca/ | College professor (Free/Libre GNU+Linux) at: http://teaching.idallen.com/ | Defend digital freedom: http://eff.org/ and have fun: http://fools.ca/ -- You received this bug notification because you
[Bug 509180] Re: ecryptfs sometimes seems to add trailing garbage to encrypted files
755fd31ebc83f02d76bcc69bacbb9104 25 1708372 33133 6 777 777 0 571 1316719634 889794256 1286771927 4096 24 b376554f519737a92ee3c49dc9126b8f 25 1708372 33133 6 777 777 0 571 1316719634 889794256 1286771927 4096 24 9898979b1fd2290e0a84b7a61a948f69 25 2100112 33133 3 777 777 0 5171 1316719634 893955992 1286771928 4096 32 b0073486c0d777d08935c2de20555c1b 25 2100112 33133 3 777 777 0 5171 1316719634 893955992 1286771928 4096 32 2fa1ea39deb352b6ae6c299e247f6984 25 6432103 33056 2 777 777 0 10240 1316720038 1169747949 1286771772 4096 40 69ea53d5d395c2b66323908936bcab27 25 6432103 33056 2 777 777 0 10240 1316720038 1169747949 1286771772 4096 40 0102ddf40cc9970703be495364f6b49d 25 6553900 33200 2 777 777 0 21562 1316720038 1169144857 1286771772 4096 64 8dd8909086e374795bccdd0cdcaec708 25 6553900 33200 2 777 777 0 21562 1316720038 1169144857 1286771772 4096 64 2729fd22c4e2dc5c7dad55efea59816c 25 5259866 33188 2 777 777 0 11632 1316719638 1295994736 1306955878 4096 40 ef56472cf83a33203cdc9f75cfc96417 25 5259866 33188 2 777 777 0 11632 1316719638 1295994736 1306955878 4096 40 47383a0471b18b60a0927c4938a73590 25 5259896 33188 2 777 777 0 364 1316719638 1295994738 1306955879 4096 24 b58ce988f987e0f2b2cdea8d37f3ce5a 25 5259896 33188 2 777 777 0 364 1316719638 1295994738 1306955879 4096 24 765ab08d4bca476c9c2c2ae77c4de04d 25 4987811 33060 14 777 777 0 423 1316720053 947301176 1286771951 4096 24 9494a2f9c673ed2841bbb5f8dbe50078 25 4987811 33060 14 777 777 0 423 1316720053 947301176 1286771951 4096 24 5a8a9d71c274d5c89c73b15ca0b942b4 25 2100801 33133 5 777 777 0 1741 1316719634 893803806 1286771929 4096 24 8687150f675e9a3ff5a554b61a93bc46 25 2100801 33133 5 777 777 0 1741 1316719634 893803806 1286771929 4096 24 083e4d0879b8e6ff9fefba0a1e310ee1 25 1705547 33248 2 777 777 0 16282 1316719610 1037740744 1286771882 4096 48 99d7d3a3ccf7ae11159914a6f1d0733e 25 1705547 33248 2 777 777 0 16282 1316719610 1037740744 1286771882 4096 48 4131baafcda44afb321152863b7738ed 25 5124379 33188 10 777 777 0 1120 1316720061 966839592 1286771948 4096 24 41d163d06d9277abbe3b0a0241b12466 25 5124379 33188 10 777 777 0 1120 1316720061 966839592 1286771948 4096 24 3d9807caa06ecd0a5e7835fff35e59d6 25 4989066 33060 2 777 777 0 26693 1316720053 1095362037 1286771940 4096 72 aae1eb503271a48de565ae98b947bc93 25 4989066 33060 2 777 777 0 26693 1316720053 1095362037 1286771940 4096 72 110f8be7ab5a7dd7df6d92bcb3108870 25 5259894 33188 2 777 777 0 265 1316719638 1295994738 1306955876 4096 24 1dac22b20b7dd28dc474306f42f07bbb 25 5259894 33188 2 777 777 0 265 1316719638 1295994738 1306955876 4096 24 083e4d0879b8e6ff9fefba0a1e310ee1 25 1705547 33248 2 777 777 0 16282 1316719610 1037740744 1286771882 4096 48 476503e7893a0a65ac507fbc8cdf8fee 25 1705547 33248 2 777 777 0 16282 1316719610 1037740744 1286771882 4096 48 136ace18c7fe1a88a05e373fd2691509 25 2100812 33133 4 777 777 0 16775 1316719634 893803738 1286771929 4096 56 22a80a8aa3cb1ed7f861e6764ffd24b8 25 2100812 33133 4 777 777 0 16775 1316719634 893803738 1286771929 4096 56 4f8b2ae505831c13ababf97d88fb9c5b 25 6444861 33188 2 777 777 0 285 1316719548 1289288995 1289289103 4096 24 5ed806ab2c77de38da87c25f57704a59 25 6444861 33188 2 777 777 0 285 1316719548 1289288995 1289289103 4096 24 1e040e3e9f7cc9090fae3d96a5cd234d 25 1705492 33248 2 777 777 0 10889 1316719610 1037672622 1286771882 4096 40 fa4951d10c02ef6042135cce2c01189f 25 1705492 33248 2 777 777 0 10889 1316719610 1037672622 1286771882 4096 40 7fbb5e5a167f24bac8469606a5d0a26a 25 1705521 33248 2 777 777 0 12765 1316719610 1037715886 1286771882 4096 48 f909799efc770c7e5275cb2587627ade 25 1705521 33248 2 777 777 0 12765 1316719610 1037715886 1286771882 4096 48 7dfae954d7c6f4787d9236c989e2217f 25 1705492 33248 2 777 777 0 10889 1316719610 1037672622 1286771882 4096 40 fa4951d10c02ef6042135cce2c01189f 25 1705492 33248 2 777 777 0 10889 1316719610 1037672622 1286771882 4096 40 1010c5075017a665a9799aede68339ac 25 2100092 33133 8 777 777 0 2636 1316719634 891569196 1286771928 4096 24 55c4334ea6da9faf5a1d3c95c1103c3e 25 2100092 33133 8 777 777 0 2636 1316719634 891569196 1286771928 4096 24 3fb139d7a83c75b221da0f1cf6226207 25 2100807 33133 6 777 777 0 1642 1316719634 889568628 1286771929 4096 24 66af1020d4cec3603b158afe92492351 25 2100807 33133 6 777 777 0 1642 1316719634 889568628 1286771929 4096 24 6259773096a72272aae4ed28a6a362f1 25 6430577 33056 2 777 777 0 20480 1316720037 1175010335 1286771771 4096 56 dac8608422c39ab642eef0100e112053 25 6430577 33056 2 777 777 0 20480 1316720037 1175010335 1286771771 4096 56 ea01946c5d66c28f3471bfc286bda3a7 25 5124374 33188 5 777 777 0 1205 1316720061 966839592 1286771948 4096 24 ea62a726ee2b908cf45086f235c2a727 25 5124374 33188 5 777 777 0 1205 1316720061 966839592 1286771948 4096 24 -- | Ian! D. Allen - idal...@idallen.ca - Ottawa, Ontario, Canada | Home Page: http://idallen.com/ Contact Improv: http://contactimprov.ca/ | College professor (Free/Libre GNU+Linux) at: http
[Bug 745836] Re: encrypted swap corrupts application stack/heap [was: soffice.bin SIGSEGV cppu::throwException()]
@Björn - yes, after this final comment I'll move to a different ecryptfs bug report (or file a new one if it doesn't exist yet). @Dustin - here are your answers. I'm only using an ecryptfs test directory (reading only; no writing) that used to be my HOME directory before I abandoned using ecryptfs. I'm not using encrypted swap. $ uname -a Linux linux 2.6.38-11-generic #50-Ubuntu SMP Mon Sep 12 21:17:25 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux $ cat /proc/swaps FilenameTypeSizeUsedPriority /dev/sda2 partition 8499196 594192 -1 $ free total used free sharedbuffers cached Mem: 81949807502036 692944 0 3582205106780 -/+ buffers/cache:20370366157944 Swap: 8499196 5941887905008 $ ls -alF /dev/mapper/cryptswap* [not using cryptswap] $ grep swap /etc/fstab UUID=02d21245-167c-48ab-811a-77b0ed45ca0e noneswapsw 0 0 $ grep swap /etc/crypttab [not using cryptswap] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/745836 Title: encrypted swap corrupts application stack/heap [was: soffice.bin SIGSEGV cppu::throwException()] To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/745836/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 745836] Re: soffice.bin crashed with SIGSEGV in cppu::throwException()
The ecryptfs bug wasn't fixed in Ubuntu 11.04 with kernel 2.6.38-11-generic x86_64 #47-Ubuntu in August. I'll run my ecryptfs read-only tests again now using the current Ubuntu kernel I have, which is: Linux linux 2.6.38-11-generic #50-Ubuntu SMP Mon Sep 12 21:17:25 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/745836 Title: soffice.bin crashed with SIGSEGV in cppu::throwException() To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/745836/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 745836] Re: soffice.bin crashed with SIGSEGV in cppu::throwException()
My testing is showing that the ecryptfs bug is still there in a fully-updated Ubuntu 11.04 on x86_64 with this kernel: Linux linux 2.6.38-11-generic #50-Ubuntu SMP Mon Sep 12 21:17:25 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux Running md5sum repeatedly over the same 17GB ecryptfs directory gives different md5sums on some of the files on some of the runs. Another fact: I am using an OCZ SSD for this file system. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/745836 Title: soffice.bin crashed with SIGSEGV in cppu::throwException() To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/745836/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 745836] Re: soffice.bin crashed with SIGSEGV in cppu::throwException()
From: https://bugs.launchpad.net/ecryptfs/+bug/509180 Linux linux 2.6.38-11-generic #47-Ubuntu SMP Fri Jul 15 19:27:09 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux Description: Ubuntu 11.04 Codename: natty After months of kernel and application crashes and corrupt files, I was ready to abandon Ubuntu 11.04 and go to some other distribution. Before doing that, I wrote a script to repeatedly md5sum the files in my ecryptfs directory and compare the results. I went single-user to ensure that nothing else was running and, sure enough, the script showed that md5sums changed randomly on files that I never touched. I went looking today and found this launchpad entry indicating that you have known for 18 months (since 9.10!) that ecryptfs is broken and is not suitable for production use. Why didn't you disable it in recent releases? My 11.04 install offered to encrypt my home directory during installation, yet you've known for 18 months that to do so would corrupt my system and crash it. I am frustrated that nobody took prompt action to disable the use of ecryptfs and to notify those of us using it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/745836 Title: soffice.bin crashed with SIGSEGV in cppu::throwException() To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/745836/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 852619] Re: pitivi crashed with PipelineError in setState(): Failure changing state of the gst.Pipeline to enum GST_STATE_PAUSED of type GstState, currently reset to NULL
On my screen: pitivi Xlib: extension RANDR missing on display :0. /usr/lib/pitivi/python/pitivi/application.py:284: Warning: g_object_set_qdata: assertion `G_IS_OBJECT (object)' failed self.mainloop.run() ERROR [15067] [0x7fb0f8730720] seeker Sep 17 10:59:29 _seekTimeoutCb: Error while seeking to position:0:10:18.092591802 format:enum GST_FORMAT_TIME of type GstFormat (/usr/lib/pitivi/python/pitivi/utils.py:318) Traceback (most recent call last): File /usr/lib/pitivi/python/pitivi/ui/mainwindow.py, line 656, in _undoCb self.app.action_log.undo() File /usr/lib/pitivi/python/pitivi/undo.py, line 165, in undo self._runStack(stack, stack.undo) File /usr/lib/pitivi/python/pitivi/undo.py, line 205, in _runStack run() File /usr/lib/pitivi/python/pitivi/undo.py, line 80, in undo self._runAction(self.done_actions, undo) File /usr/lib/pitivi/python/pitivi/undo.py, line 72, in _runAction method() File /usr/lib/pitivi/python/pitivi/projectmanager.py, line 50, in undo self.project.setSettings(self.oldsettings) File /usr/lib/pitivi/python/pitivi/project.py, line 125, in setSettings self._projectSettingsChanged() File /usr/lib/pitivi/python/pitivi/project.py, line 202, in _projectSettingsChanged self.pipeline.pause() File /usr/lib/pitivi/python/pitivi/pipeline.py, line 295, in pause self.setState(STATE_PAUSED) File /usr/lib/pitivi/python/pitivi/pipeline.py, line 269, in setState raise PipelineError(Failure changing state of the gst.Pipeline to %r, currently reset to NULL % state) pitivi.pipeline.PipelineError: Failure changing state of the gst.Pipeline to enum GST_STATE_PAUSED of type GstState, currently reset to NULL ** 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/852619 Title: pitivi crashed with PipelineError in setState(): Failure changing state of the gst.Pipeline to enum GST_STATE_PAUSED of type GstState, currently reset to NULL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pitivi/+bug/852619/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 509180] Re: ecryptfs sometimes seems to add trailing garbage to encrypted files
@Dustin Things that might make a difference: 64-bit SMP kernel on AMD quad-core, 120GB SSD hard disk, 8GB memory. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/509180 Title: ecryptfs sometimes seems to add trailing garbage to encrypted files To manage notifications about this bug go to: https://bugs.launchpad.net/ecryptfs/+bug/509180/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 509180] Re: ecryptfs sometimes seems to add trailing garbage to encrypted files
Linux linux 2.6.38-11-generic #47-Ubuntu SMP Fri Jul 15 19:27:09 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux Description:Ubuntu 11.04 Codename: natty After months of kernel and application crashes and corrupt files, I was ready to abandon Ubuntu 11.04 and go to some other distribution. Before doing that, I wrote a script to repeatedly md5sum the files in my ecryptfs directory and compare the results. I went single-user to ensure that nothing else was running and, sure enough, the script showed that md5sums changed randomly on files that I never touched. I went looking today and found this launchpad entry indicating that you have known for 18 months (since 9.10!) that ecryptfs is broken and is not suitable for production use. Why didn't you disable it in recent releases? My 11.04 install offered to encrypt my home directory during installation, yet you've known for 18 months that to do so would corrupt my system and crash it. I am frustrated that nobody took prompt action to disable the use of ecryptfs and to notify those of us using it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/509180 Title: ecryptfs sometimes seems to add trailing garbage to encrypted files To manage notifications about this bug go to: https://bugs.launchpad.net/ecryptfs/+bug/509180/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 669211] Re: Xpdf segfaults on start in libpoppler.so.7
Same problem in natty with xpdf 3.02-12ubuntu2 and any PDF file. evince works fine. $ gdb xpdf GNU gdb (Ubuntu/Linaro 7.2-1ubuntu11) 7.2 Copyright (C) 2010 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type show copying and show warranty for details. This GDB was configured as x86_64-linux-gnu. For bug reporting instructions, please see: http://www.gnu.org/software/gdb/bugs/... Reading symbols from /usr/bin/xpdf...(no debugging symbols found)...done. (gdb) run /tmp/gr.pdf Starting program: /usr/bin/xpdf /tmp/gr.pdf Program received signal SIGSEGV, Segmentation fault. 0x771aeecb in GlobalParams::findFontFile(GooString*, char**) () from /usr/local/lib/libpoppler.so.13 (gdb) bt #0 0x771aeecb in GlobalParams::findFontFile(GooString*, char**) () from /usr/local/lib/libpoppler.so.13 #1 0x77197b66 in GfxFont::findExtFontFile() () from /usr/local/lib/libpoppler.so.13 #2 0x771980bb in Gfx8BitFont::Gfx8BitFont(XRef*, char*, Ref, GooString*, GfxFontType, Dict*) () from /usr/local/lib/libpoppler.so.13 #3 0x7719b43c in GfxFont::makeFont(XRef*, char*, Ref, Dict*) () from /usr/local/lib/libpoppler.so.13 #4 0x7719b6cf in GfxFontDict::GfxFontDict(XRef*, Ref*, Dict*) () from /usr/local/lib/libpoppler.so.13 #5 0x77183be2 in GfxResources::GfxResources(XRef*, Dict*, GfxResources*) () from /usr/local/lib/libpoppler.so.13 #6 0x77195c2a in Gfx::Gfx(XRef*, OutputDev*, int, Dict*, Catalog*, double, double, PDFRectangle*, PDFRectangle*, int, bool (*)(void*), void*) () from /usr/local/lib/libpoppler.so.13 #7 0x771c6e87 in Page::createGfx(OutputDev*, double, double, int, bool, bool, int, int, int, int, bool, Catalog*, bool (*)(void*), void*, bool (*)(Annot*, void*), void*) () from /usr/local/lib/libpoppler.so.13 #8 0x771c710d in Page::displaySlice(OutputDev*, double, double, int, bool, bool, int, int, int, int, bool, Catalog*, bool (*)(void*), void*, bool (*)(Annot*, void*), void*) () from /usr/local/lib/libpoppler.so.13 #9 0x004149bc in ?? () #10 0x00417d71 in ?? () #11 0x0041a7ad in ?? () #12 0x00412755 in ?? () #13 0x00426e18 in ?? () #14 0x00418bdd in ?? () #15 0x00427b7c in ?? () #16 0x765aceff in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6 #17 0x0040adf9 in ?? () #18 0x7fffdf88 in ?? () #19 0x001c in ?? () #20 0x0002 in ?? () #21 0x7fffe439 in ?? () #22 0x7fffe447 in ?? () #23 0x in ?? () (gdb) quit -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/669211 Title: Xpdf segfaults on start in libpoppler.so.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xpdf/+bug/669211/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 788227] Re: Synaptic Package Manager fails with g_dbus_connection_real_closed
Ubuntu natty and synaptic 0.75.1ubuntu2 when run as root from terminal command line: # synaptic Xlib: extension RANDR missing on display :0. g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. Terminated Exit 143 Opens fine when run as non-root. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/788227 Title: Synaptic Package Manager fails with g_dbus_connection_real_closed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zeitgeist-datahub/+bug/788227/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 809002] Re: meld GLib-GIO:ERROR initable_init: assertion failed: (connection-initialization_error == NULL)
** 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/809002 Title: meld GLib-GIO:ERROR initable_init: assertion failed: (connection-initialization_error == NULL) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/meld/+bug/809002/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 809002] Re: meld GLib-GIO:ERROR initable_init: assertion failed: (connection-initialization_error == NULL)
last part of strace:
open(/usr/local/lib/libdbusmenu-glib.so.3, O_RDONLY) = 3
read(3, \177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0\0\1\0\0\0\20S\0\0\0\0\0\0...,
832) = 832
fstat(3, {st_mode=S_IFREG|0644, st_size=101616, ...}) = 0
mmap(NULL, 2197232, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0x7fddce0f1000
mprotect(0x7fddce108000, 2097152, PROT_NONE) = 0
mmap(0x7fddce308000, 8192, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x17000) = 0x7fddce308000
close(3)= 0
mprotect(0x7fddce308000, 4096, PROT_READ) = 0
mprotect(0x7fddce51a000, 4096, PROT_READ) = 0
mprotect(0x7fddce72, 4096, PROT_READ) = 0
munmap(0x7fddda214000, 75221) = 0
sched_get_priority_min(SCHED_OTHER) = 0
sched_get_priority_max(SCHED_OTHER) = 0
mmap(NULL, 8392704, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS|MAP_STACK,
-1, 0) = 0x7fddcd8f
mprotect(0x7fddcd8f, 4096, PROT_NONE) = 0
clone(child_stack=0x7fddce0effd0,
flags=CLONE_VM|CLONE_FS|CLONE_FILES|CLONE_SIGHAND|CLONE_THREAD|CLONE_SYSVSEM|CLONE_SETTLS|CLONE_PARENT_SETTID|CLONE_CHILD_CLEARTID,
parent_tidptr=0x7fddce0f09d0, tls=0x7fddce0f0700, child_tidptr=0x7fddce0f09d0)
= 25392
futex(0x7fddd8f601c0, FUTEX_WAIT_PRIVATE, 2, NULL) = -1 EAGAIN (Resource
temporarily unavailable)
futex(0x7fddd8f601c0, FUTEX_WAKE_PRIVATE, 1) = 0
futex(0x1d3b7b8, FUTEX_WAIT_PRIVATE, 2, NULL) = 0
futex(0x1d3b7b8, FUTEX_WAKE_PRIVATE, 1) = 0
mmap(NULL, 134217728, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS|MAP_NORESERVE, -1,
0) = 0x7fddc58f
munmap(0x7fddc58f, 4096)= 0
munmap(0x7fddcc00, 26148864)= 0
mprotect(0x7fddc800, 135168, PROT_READ|PROT_WRITE) = 0
futex(0x7fddd83327c8, FUTEX_WAKE_PRIVATE, 1) = 0
futex(0x7fddd8333148, FUTEX_WAKE_PRIVATE, 1) = 0
futex(0x1d3b7b8, FUTEX_WAIT_PRIVATE, 2, NULL) = -1 EAGAIN (Resource temporarily
unavailable)
futex(0x1d3b7b8, FUTEX_WAIT_PRIVATE, 2, NULL) = -1 EAGAIN (Resource temporarily
unavailable)
futex(0x1d3b7b8, FUTEX_WAKE_PRIVATE, 1) = 0
futex(0x1d3b7b8, FUTEX_WAKE_PRIVATE, 1) = 0
futex(0x7fddd7cd4988, FUTEX_WAIT_PRIVATE, 2, NULL) = 0
futex(0x7fddd7cd4988, FUTEX_WAKE_PRIVATE, 1) = 0
futex(0x7fddd83327c8, FUTEX_WAIT_PRIVATE, 2, NULL) = -1 EAGAIN (Resource
temporarily unavailable)
futex(0x7fddd83327c8, FUTEX_WAKE_PRIVATE, 1) = 0
futex(0x1d3b7b8, FUTEX_WAIT_PRIVATE, 2, NULL) = -1 EAGAIN (Resource temporarily
unavailable)
futex(0x1d3b7b8, FUTEX_WAKE_PRIVATE, 1) = 0
futex(0x7fddd8333148, FUTEX_WAIT_PRIVATE, 2, NULL) = -1 EAGAIN (Resource
temporarily unavailable)
futex(0x1cbe1f4, FUTEX_WAKE_OP_PRIVATE, 1, 1, 0x1cbe1f0, {FUTEX_OP_SET, 0,
FUTEX_OP_CMP_GT, 1}) = 1
futex(0x7fddd8333148, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0x7fddd8f601c0, FUTEX_WAKE_PRIVATE, 1) = 0
futex(0x7fddd7cd49e8, FUTEX_WAKE_PRIVATE, 1) = 0
futex(0x7fddd7cd49e8, FUTEX_WAKE_PRIVATE, 1) = 0
futex(0x7fddd83327c8, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0x7fddd83327c8, FUTEX_WAIT_PRIVATE, 2, NULL) = -1 EAGAIN (Resource
temporarily unavailable)
futex(0x7fddd83327c8, FUTEX_WAKE_PRIVATE, 1) = 0
futex(0x7fddd8333248, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0x1d3b7b8, FUTEX_WAKE_PRIVATE, 1) = 0
futex(0x7fddd7cd49e8, FUTEX_WAKE_PRIVATE, 1) = 0
write(2, **\nGLib-GIO:ERROR:/build/buildd/..., 152) = 152
rt_sigprocmask(SIG_UNBLOCK, [ABRT], NULL, 8) = 0
tgkill(25389, 25389, SIGABRT) = 0
--- SIGABRT (Aborted) @ 0 (0) ---
+++ killed by SIGABRT (core dumped) +++
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/809002
Title:
meld GLib-GIO:ERROR initable_init: assertion failed:
(connection-initialization_error == NULL)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/meld/+bug/809002/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 788227] Re: Synaptic Package Manager fails with g_dbus_connection_real_closed
Last part of strace (natty and synaptic 0.75.1ubuntu2):
open(/var/lib/dbus/machine-id, O_RDONLY) = 15
fstat(15, {st_mode=S_IFREG|0644, st_size=33, ...}) = 0
read(15, d4f4c42dcd97e0e63ab16fa5000e..., 33) = 33
close(15) = 0
access(/root, F_OK) = 0
stat(/root, {st_mode=S_IFDIR|0700, st_size=4096, ...}) = 0
access(/root/.config, F_OK) = 0
stat(/root/.config, {st_mode=S_IFDIR|0700, st_size=4096, ...}) = 0
access(/root/.config/ibus, F_OK) = 0
stat(/root/.config/ibus, {st_mode=S_IFDIR|0700, st_size=4096, ...}) = 0
access(/root/.config/ibus/bus, F_OK) = 0
stat(/root/.config/ibus/bus, {st_mode=S_IFDIR|0700, st_size=4096, ...}) = 0
chmod(/root/.config/ibus/bus, 0700) = 0
stat(/root/.config/ibus/bus, {st_mode=S_IFDIR|0700, st_size=4096, ...}) = 0
getuid()= 0
open(/root/.config/ibus/bus/d4f4c42dcd97e0e63ab16fa5000e-unix-0,
O_RDONLY) = -1 ENOENT (No such file or directory)
inotify_init1(O_CLOEXEC)= 15
fstat(15, {st_mode=0600, st_size=0, ...}) = 0
fcntl(15, F_GETFL) = 0 (flags O_RDONLY)
fcntl(15, F_SETFL, O_RDONLY|O_NONBLOCK) = 0
inotify_add_watch(15, /root/.config/ibus/bus,
IN_MODIFY|IN_ATTRIB|IN_CLOSE_WRITE|IN_MOVED_FROM|IN_MOVED_TO|IN_CREATE|IN_DELETE|IN_DELETE_SELF|IN_MOVE_SELF|IN_UNMOUNT|IN_ONLYDIR)
= 1
brk(0xb8) = 0xb8
stat(/usr/lib/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-xpm.so,
{st_mode=S_IFREG|0644, st_size=26960, ...}) = 0
open(/usr/lib/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-xpm.so, O_RDONLY)
= 16
read(16, \177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0\0\1\0\0\0@\24\0\0\0\0\0\0...,
832) = 832
fstat(16, {st_mode=S_IFREG|0644, st_size=26960, ...}) = 0
mmap(NULL, 2122208, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 16, 0) =
0x7f259f3b3000
mprotect(0x7f259f3b9000, 2093056, PROT_NONE) = 0
mmap(0x7f259f5b8000, 8192, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 16, 0x5000) = 0x7f259f5b8000
close(16) = 0
mprotect(0x7f259f5b8000, 4096, PROT_READ) = 0
poll([{fd=3, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=3, revents=POLLOUT}])
writev(3, [{+\0\1\0, 4}, {NULL, 0}, {, 0}], 3) = 4
poll([{fd=3, events=POLLIN}], 1, -1)= 1 ([{fd=3, revents=POLLIN}])
read(3, \1\1\222\1\0\0\0\0\v\0@\1\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0,
4096) = 32
read(3, 0x9598c4, 4096) = -1 EAGAIN (Resource temporarily
unavailable)
read(3, 0x9598c4, 4096) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=4, events=POLLIN}, {fd=3, events=POLLIN}, {fd=15, events=POLLIN}], 3,
0) = 0 (Timeout)
poll([{fd=4, events=POLLIN}, {fd=3, events=POLLIN}, {fd=15, events=POLLIN}], 3,
0) = 0 (Timeout)
read(3, 0x9598c4, 4096) = -1 EAGAIN (Resource temporarily
unavailable)
fstat(1, {st_mode=S_IFCHR|0600, st_rdev=makedev(136, 4), ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7f25b5133000
write(1, g_dbus_connection_real_closed: R..., 151) = 151
tgkill(26905, 26905, SIGTERM) = 0
--- SIGTERM (Terminated) @ 0 (0) ---
+++ killed by SIGTERM +++
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/788227
Title:
Synaptic Package Manager fails with g_dbus_connection_real_closed
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zeitgeist-datahub/+bug/788227/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 806749] [NEW] options nomargins dont_wrap_pre and width strip spaces
Public bug reported: !-- Command line: lynx -dump -force_html -nomargins -dont_wrap_pre -width=70 THISFILE Incorrect output (missing spaces between words when word ends at line end): x -- html head titleLynx Bug/title /head body p x /p /body /html ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: lynx 2.8.8dev.7-1 ProcVersionSignature: Ubuntu 2.6.38-10.46-generic 2.6.38.7 Uname: Linux 2.6.38-10-generic x86_64 Architecture: amd64 Date: Wed Jul 6 21:27:29 2011 EcryptfsInUse: Yes InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1) PackageArchitecture: all SourcePackage: lynx-cur UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lynx-cur (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug natty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/806749 Title: options nomargins dont_wrap_pre and width strip spaces To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lynx-cur/+bug/806749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 806749] Re: options nomargins dont_wrap_pre and width strip spaces
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/806749 Title: options nomargins dont_wrap_pre and width strip spaces To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lynx-cur/+bug/806749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 806749] Re: options nomargins dont_wrap_pre and width strip spaces
Related bug: !-- Command line: lynx -dump -force_html -nomargins -dont_wrap_pre -width=71 THISFILE Incorrect output (not wrapped at 71): xxx xxx xxx x xxx xx YYY YYY YYY Y YYY Y zzz zzz zzz z zzz z AAA AAA AAA A AAA A Removing -dont_wrap_pre produces correct output, even though it shouldn't have any effect since no pre is being used: Command line: lynx -dump -force_html -nomargins -width=71 THISFILE Correct output (wrapped at 71): xxx xxx xxx x xxx xx YYY YYY YYY Y YYY Y zzz zzz zzz z zzz z AAA AAA AAA A AAA A -- html head titleLynx Bug/title /head body p xxx xxx xxx x xxx xx YYY YYY YYY Y YYY Y zzz zzz zzz z zzz z AAA AAA AAA A AAA A /p /body /html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/806749 Title: options nomargins dont_wrap_pre and width strip spaces To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lynx-cur/+bug/806749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 806749] Re: options nomargins dont_wrap_pre and width strip spaces
Note that Launchpad mangled and wrapped my bug report, above, so that the incorrect and correct outputs look the same. Try the input file and the command line to see that they are not the same output. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/806749 Title: options nomargins dont_wrap_pre and width strip spaces To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lynx-cur/+bug/806749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 801449] Re: gconftool-2 crashed with SIGABRT in raise()
** 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/801449 Title: gconftool-2 crashed with SIGABRT in raise() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/801449/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 801358] Re: compiz crashed with SIGSEGV in CompositeScreen::damageRegion()
** 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/801358 Title: compiz crashed with SIGSEGV in CompositeScreen::damageRegion() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/801358/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 777882] Re: xmodmap not honored in natty
This xmodmap work-around works for me: keycode 66 = Control_L clear Lock add Control = Control_L see http://ubuntuforums.org/showthread.php?t=1743145 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/777882 Title: xmodmap not honored in natty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/777882/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 765230] Re: long sleep in boot process
2.6.38-10 improved things from 145 seconds down to 9 seconds, yes: Jun 16 09:40:23 kernel: [1.044704] UDP-Lite hash table entries: 4096 (order: 5, 131072 bytes) Jun 16 09:40:23 kernel: [1.044798] NET: Registered protocol family 1 Jun 16 09:40:23 kernel: [ 10.470269] pci :05:00.0: Boot video device Jun 16 09:40:23 kernel: [ 10.470286] PCI: CLS 64 bytes, default 64 Still - 9 seconds delay? What takes 9 seconds in a world of quad-core 64-bit CPUs? ASUSTeK M4A79T Deluxe AMD Phenom(tm) II X4 965 American Megatrends Inc. BIOS Revision: 8.15 Version: 1303 Release Date: 06/10/2009 05:00.0 VGA compatible controller: ATI Technologies Inc FireMV 2250 05:00.1 Display controller: ATI Technologies Inc FireMV 2250 (Secondary) Ubuntu 11.04 Linux linux 2.6.38-10-generic #44-Ubuntu SMP Thu Jun 2 21:32:22 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux sda: OCZ-VERTEX2 120GB -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/765230 Title: long sleep in boot process To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/765230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 637418] Re: soffice.bin crashed with SIGSEGV in cppu::throwException()
On Sun, Jun 05, 2011 at 10:14:20AM -, Rolf Leggewie wrote: Ian, are you still experiencing this? I don't use OO enough to know if it's still there. Did you not touch OOo for a while before going back and then the program crashed? I think this may be a dupe of bug 793075. I don't think this was after being away for a while, but I don't remember for sure. -- | Ian! D. Allen - idal...@idallen.ca - Ottawa, Ontario, Canada | Home Page: http://idallen.com/ Contact Improv: http://contactimprov.ca/ | College professor (Free/Libre GNU+Linux) at: http://teaching.idallen.com/ | Defend digital freedom: http://eff.org/ and have fun: http://fools.ca/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/637418 Title: soffice.bin crashed with SIGSEGV in cppu::throwException() -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 776944] [NEW] package atop 1.26-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: Binary package hint: atop It refused to handle the year 1969 in /var/lib/logrotate/status I changed all the 1969 to 1970 and the package installed and updated all the years to 2011. ProblemType: Package DistroRelease: Ubuntu 11.04 Package: atop 1.26-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.35-24.42-powerpc 2.6.35.8 Uname: Linux 2.6.35-24-powerpc ppc AptOrdering: atop: Configure Architecture: powerpc Date: Wed May 4 01:06:45 2011 ErrorMessage: subprocess installed post-installation script returned error exit status 1 SourcePackage: atop Title: package atop 1.26-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to natty on 2011-05-03 (0 days ago) ** Affects: atop (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package natty powerpc -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/776944 Title: package atop 1.26-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 776944] Re: package atop 1.26-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/776944 Title: package atop 1.26-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 654382] Re: soffice.bin crashed with SIGSEGV
That bug was four months ago. I don't run that software or that operating system any more. No further information. P.S. There is still no Report a Bug entry under Help in OpenOffice.org 3.2.1 OOO320m19 (Build:9505) ooo-build 3.2.1.4, Ubuntu package 1:3.2.1-7ubuntu1.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/654382 Title: soffice.bin crashed with SIGSEGV -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 714895] [NEW] man page error for -S/--silent option
Public bug reported: Binary package hint: curl In man curl change this: -S/--silent to this: -s/--silent under the description for -v/--verbose (The S must be lower-case.) ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: curl 7.21.0-1ubuntu1 ProcVersionSignature: Ubuntu 2.6.35-25.44-generic 2.6.35.10 Uname: Linux 2.6.35-25-generic x86_64 Architecture: amd64 Date: Mon Feb 7 18:00:04 2011 EcryptfsInUse: Yes InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) ProcEnviron: LC_CTYPE=en_CA.utf8 LC_COLLATE=C PATH=(custom, user) LANG=C SHELL=/bin/bash SourcePackage: curl ** Affects: curl (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug maverick -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/714895 Title: man page error for -S/--silent option -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 714895] Re: man page error for -S/--silent option
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/714895 Title: man page error for -S/--silent option -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 711799] Re: e2fsprogs wrongly identifies ext4 as mounted
Same error, different circumstances:
# fsck.ext4 /dev/sde1
e2fsck 1.41.12 (17-May-2010)
fsck.ext4: Group descriptors look bad... trying backup blocks...
fsck.ext4: Bad magic number in super-block when using the backup blocks
fsck.ext4: going back to original superblock
fsck.ext4: Device or resource busy while trying to open /dev/sde1
Filesystem mounted or opened exclusively by another program?
The bug above is that the program opens /dev/sde1 once, forgets to close it,
then tries to open it a second time and fails. Found with strace:
[...]
write(1, fsck.ext4: Group descriptors loo..., 65) = 65
close(3)= 0
munmap(0x7f7d658b7000, 483328) = 0
open(/dev/sde1, O_RDWR|O_EXCL)= 3
ioctl(3, BLKROGET, 0x7fffe00b6bfc) = 0
uname({sys=Linux, node=idallen-oak.home.idallen.ca, ...}) = 0
lseek(3, 134217728, SEEK_SET) = 134217728
read(3, a%\20\217\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0...,
1024) = 1024
write(2, fsck.ext4, 9)= 9
write(2, : , 2) = 2
write(2, Bad magic number in super-block, 31) = 31
write(2, , 1)= 1
write(2, when using the backup blocks, 28) = 28
ioctl(2, SNDCTL_TMR_TIMEBASE or TCGETS, {B38400 opost isig icanon echo ...}) = 0
ioctl(2, SNDCTL_TMR_TIMEBASE or TCGETS, {B38400 opost isig icanon echo ...}) = 0
write(2, \n, 1) = 1
write(1, fsck.ext4: going back to origina..., 45) = 45
open(/dev/sde1, O_RDWR|O_EXCL)= -1 EBUSY (Device or resource busy)
write(2, fsck.ext4, 9)= 9
write(2, : , 2) = 2
write(2, Device or resource busy, 23) = 23
write(2, , 1)= 1
write(2, while trying to open /dev/sde1, 30) = 30
ioctl(2, SNDCTL_TMR_TIMEBASE or TCGETS, {B38400 opost isig icanon echo ...}) = 0
ioctl(2, SNDCTL_TMR_TIMEBASE or TCGETS, {B38400 opost isig icanon echo ...}) = 0
write(2, \n, 1) = 1
write(1, Filesystem mounted or opened exc..., 61) = 61
exit_group(8) = ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/711799
Title:
e2fsprogs wrongly identifies ext4 as mounted
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 697641] Re: Can't fsck broken partition from live CD
fsck.ext4 has a bug where it tries to double-open the partition. See: 711799e2fsprogs wrongly identifies ext4 as mounted -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/697641 Title: Can't fsck broken partition from live CD -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 711799] Re: e2fsprogs wrongly identifies ext4 as mounted
This one-line patch - add ext2fs_close(fs) in unix.c - seems to fix it:
if ((orig_retval == 0) retval != 0) {
com_err(ctx-program_name, retval,
when using the backup blocks);
printf(_(%s: going back to original
superblock\n), ctx-program_name);
+ ext2fs_close(fs);
ctx-superblock = orig_superblock;
retval = try_open_fs(ctx, flags, io_ptr, fs);
}
No more device busy.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/711799
Title:
e2fsprogs wrongly identifies ext4 as mounted
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 591104] Re: wrong xinerama scroll/pan using two cards three monitors
The Ubuntu bug triage system is broken if a bug reported by Ian gets thrown out by Bryce because Bryce doesn't like how someone else (James) commented on the bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/591104 Title: wrong xinerama scroll/pan using two cards three monitors -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 682211] [NEW] lastcomm cannot find /var/account/pacct
Public bug reported: Binary package hint: acct Default install of acct package doesn't enable lastcomm to work: PRE # apt-get install acct Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: acct 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 111kB of archives. After this operation, 360kB of additional disk space will be used. Get:1 http://ca.archive.ubuntu.com/ubuntu/ maverick/main acct i386 6.5.4-2ubuntu1 [111kB] 0% [1 acct 0B/111kB 0%] Fetched 111kB in 0s (115kB/s) Selecting previously deselected package acct. (Reading database ... 125574 files and directories currently installed.) Unpacking acct (from .../acct_6.5.4-2ubuntu1_i386.deb) ... Processing triggers for doc-base ... Processing 1 added doc-base file(s)... Registering documents with scrollkeeper... Processing triggers for install-info ... Processing triggers for man-db ... Processing triggers for ureadahead ... Setting up acct (6.5.4-2ubuntu1) ... Turning on process accounting, file set to '/var/log/account/pacct'. * Done. # lastcomm couldn't open file '/var/account/pacct': No such file or directory # ls -l /var/account ls: cannot access /var/account: No such file or directory # ln -s log/account /var/account # lastcomm bash Froot pts/0 0.00 secs Fri Nov 19 00:54 ln root pts/0 0.00 secs Fri Nov 19 00:54 bash Froot pts/0 0.00 secs Fri Nov 19 00:54 ls root pts/0 0.00 secs Fri Nov 19 00:54 bash Froot pts/0 0.00 secs Fri Nov 19 00:54 lastcomm root pts/0 0.00 secs Fri Nov 19 00:54 bash Froot pts/0 0.00 secs Fri Nov 19 00:54 lastcomm root pts/0 0.00 secs Fri Nov 19 00:54 [...etc...] ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: acct 6.5.4-2ubuntu1 ProcVersionSignature: Ubuntu 2.6.35-22.35-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic x86_64 Architecture: amd64 Date: Sat Nov 27 14:07:58 2010 EcryptfsInUse: Yes InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) ProcEnviron: LC_CTYPE=en_CA.utf8 LC_COLLATE=C PATH=(custom, user) LANG=C SHELL=/bin/bash SourcePackage: acct ** Affects: acct (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug maverick -- lastcomm cannot find /var/account/pacct https://bugs.launchpad.net/bugs/682211 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 682211] Re: lastcomm cannot find /var/account/pacct
-- lastcomm cannot find /var/account/pacct https://bugs.launchpad.net/bugs/682211 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 650539] Re: SRU: Launching a Qt app crashes X when using Xinerama
I followed the source-building and editing steps in #95 JMason wrote on 2010-10-23 and I finally have an Xorg that doesn't crash. Linux ian 2.6.35-22-generic #35-Ubuntu SMP Sat Oct 16 20:45:36 UTC 2010 x86_64 GNU/Linux No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 10.10 Release:10.10 Codename: maverick Finally - this has been a problem for over a month now. -- SRU: Launching a Qt app crashes X when using Xinerama https://bugs.launchpad.net/bugs/650539 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to qt4-x11 in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
