** Summary changed:
- blueman applet crashed with DBusException in call_blocking():
org.openobex.Error.InvalidArguments: Invalid path
+ Problem report is damaged, 'incorrect padding'
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
For the 'Incorrect padding' issue, Bug #1012358. (Leaving this as non-
duplicate, since the reporter has other 'damaged' errors besides that
one.)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
Sorry, but 5.0.0-1ubuntu1 didn't fix this. In Utopic, with the same 'The
Snowman' DVD as before, I still get:
*** Zero check failed in src/ifo_read.c:903
for pgc-subp_control[i] = 0x0001
*** Zero check failed in src/ifo_read.c:903
for pgc-subp_control[i] = 0x0001
*** Zero check
I acknowledge that (and as I said, it hasn't really caused any issues
with the backups), I was just responding to this being fixed (above).
If it's not really an issue in the code, maybe we should close this as
invalid? (Although I could argue that the message makes it seem as if
there is a
The community wiki currently claims that the default editor for visudo
has been sensible-editor since 8.10 [1]. But for me in both 12.04 and
14.04, `sudo visudo` still launches /etc/alternatives/editor, so select-
editor doesn't actually change visudo's editor; for that I have to run
`sudo
Public bug reported:
The setup for unlocking an encrypted volume during boot using (only) a
keyfile (on a detachable USB drive) usually calls for a keyscript to be
specified as one of the encrypted volume's options. But with systemd,
such encrypted volumes can only be unlocked during boot by
I can, but it'll be hard to get definitive evidence as the phenomenon
can be quite elusive, and I cannot run the daily for very long periods
(as it gets in the way of productivity). Obviously, if I catch it even
once on the daily, it'll be proof enough that the issue persists, but on
the other
apport information
** Attachment added: MonitorsUser.xml.txt
https://bugs.launchpad.net/bugs/1345573/+attachment/4404599/+files/MonitorsUser.xml.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: UdevLog.txt
https://bugs.launchpad.net/bugs/1345573/+attachment/4404605/+files/UdevLog.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: CurrentDmesg.txt
https://bugs.launchpad.net/bugs/1345573/+attachment/4404592/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.launchpad.net/bugs/1345573/+attachment/4404600/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: BootLog.gz
https://bugs.launchpad.net/bugs/1345573/+attachment/4404591/+files/BootLog.gz
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: LightdmLog.txt
https://bugs.launchpad.net/bugs/1345573/+attachment/4404596/+files/LightdmLog.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
apport information
** Tags added: apport-collected compiz-0.9 ubuntu
** Description changed:
Since upgrading HWE from -lts-saucy to -lts-trusty, I have had recurring
graphical glitches on screen, with short black horizontal lines
appearing briefly on screen (on top of normal contents),
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.launchpad.net/bugs/1345573/+attachment/4404602/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: Lspci.txt
https://bugs.launchpad.net/bugs/1345573/+attachment/4404597/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: Dependencies.txt
https://bugs.launchpad.net/bugs/1345573/+attachment/4404593/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: xdpyinfo.txt
https://bugs.launchpad.net/bugs/1345573/+attachment/4404610/+files/xdpyinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: UdevDb.txt
https://bugs.launchpad.net/bugs/1345573/+attachment/4404604/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: XorgLogOld.txt
https://bugs.launchpad.net/bugs/1345573/+attachment/4404608/+files/XorgLogOld.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: ProcEnviron.txt
https://bugs.launchpad.net/bugs/1345573/+attachment/4404601/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: UnitySupportTest.txt
https://bugs.launchpad.net/bugs/1345573/+attachment/4404606/+files/UnitySupportTest.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: ProcModules.txt
https://bugs.launchpad.net/bugs/1345573/+attachment/4404603/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: Xrandr.txt
https://bugs.launchpad.net/bugs/1345573/+attachment/4404609/+files/Xrandr.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: Lsusb.txt
https://bugs.launchpad.net/bugs/1345573/+attachment/4404598/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: XorgLog.txt
https://bugs.launchpad.net/bugs/1345573/+attachment/4404607/+files/XorgLog.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: DpkgLog.txt
https://bugs.launchpad.net/bugs/1345573/+attachment/4404594/+files/DpkgLog.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
Hi Christopher, the apport-collected data above was gathered from my
main desktop, which only has Intel graphics. (I mentioned the other
system with Radeon just because it *didn't* suffer from this problem
despite having the same software. I no longer have access to that system
so unfortunately I
Just adding a note that this does still occur under 14.04, to which I
recently upgraded. Naturally this was to be expected, given that the
issue first occurred after switching to the Trusty HWE pack in 12.04.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Haven't seen this once since upgrading to 16.04 back in April, so I'm
pretty sure the issue has been fixed. Yay!
** Changed in: xorg (Ubuntu)
Status: Expired => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Bug watch added: Debian Bug tracker #582067
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=582067
** Also affects: coreutils (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=582067
Importance: Unknown
Status: Unknown
--
You received this bug notification
Depending on use case, using `fmt -w 80` instead of fold may do for a
workaround.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to coreutils in Ubuntu.
https://bugs.launchpad.net/bugs/647462
Title:
fold works wrong with
Public bug reported:
For optimizing files in-place with jpegtran, especially from scripts and
when dealing with lots of pictures, it's handy to be able to specify
input file as -outfile.
But there's a catch:
Steps to reproduce:
0. Have a large JPEG file, or, alternatively, somewhat slow CPU
1.
** Description changed:
- GDebi doesn't handle Firefox "open with" option instead of "save file".
- It will open GDebi but when presing to install the pachage it will close.
+ When launched from Firefox with the "open with" function, GDebi is
+ unable to complete installing the package. The
Public bug reported:
== Steps to reproduce ==
`wget -q https://www.google.com/ &`
== What happens ==
wget says it's "Redirecting output to 'wget-log'" and creates an empty wget-log
file in the current directory.
== What I expect to happen ==
No wget-log file to be created.
== Details ==
Red Hat issue: https://bugzilla.redhat.com/show_bug.cgi?id=1484411
"Running wget with -O and -q in the background yields a file wget-log"
Related but (FWICT) not precisely the same issues upstream:
* https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888691 "wget -b produces
empty wget-log file"
** Summary changed:
- wget --quite --background leaves a wget.log file
+ wget --quiet --background leaves a wget.log file
** Description changed:
Binary package hint: wget
- wget --quite --background leaves a 0 byte wget.log file
+ wget --quiet --background leaves a 0 byte wget.log file
I've hit an issue, which I believe I've now isolated to have come from
upgrading fontconfig (and related packages) from 2.12.6-0ubuntu2 to
2.12.6-0ubuntu2.3 from -proposed: if I start Firefox and afterwards
start Gparted or Synaptic, Firefox starts eating up all of my CPU.
Eventually all letters
I removed all but Desktop Icons, Ubuntu AppIndicators and Ubuntu Dock,
rebooted and then reproduced the issue. Luckily I've found one way to
reproduce this, albeit somewhat convoluted and still a bit unreliable,
involving Synaptic and window tiling. And as it doesn't seem to trigger
the issue when
Thanks for the instructions, Daniel! I found no crash files either
locally or online, so I've implemented the workaround now, and will try
to trigger the crash again.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wayland in
Turns out the online service was just a little slow to update, and there
are in fact reports sent. But the only one post-20.04-upgrade is [1]
from last week, which is a gnome-shell crash and IIRC, unrelated to the
terminal issue here. It seemed to be triggered by something related to
media files
** Attachment added: "syslog.5-excerpt.log"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1877568/+attachment/5369829/+files/syslog.5-excerpt.log
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wayland in Ubuntu.
Happened again:
May 11 17:05:50 saegusa gnome-shell[3619]: WL: compositor bug: The
compositor tried to use an object from one client in a 'wl_pointer.enter' for a
different client.
May 11 17:05:50 saegusa gnome-shell[3619]: WL: error in client
communication (pid 5170)
May 11
After doing manual dconf cleanup, I've been unable to reproduce the
issue. That's since posting the previous comment, so a few days now. So
I think I'll hold off on reporting this upstream for the time being, but
I'll go ahead and do that if the problem still manifests itself.
Thanks again,
Public bug reported:
The man page for logrotate says "Each configuration file can set global
options (local definitions override global ones, and later definitions
override earlier ones)". This is inconsistent with how it actually
behaves.
== Steps to reproduce ==
$ logrotate --version
In fact the man page seems to be completely out of sync with reality.
None of minage, maxage, minsize and maxsize appear to work at all
despite being documented there. Minage is read at least (according to
debug output), but then still ignored. Specifying minsize or maxsize has
no effect, logs are
46 matches
Mail list logo
