This also affects libdune-grid-dev by breaking the `subsamplingvtktest`
test of the package. Steps to reproduce this locally:
1. Create a new dune module using `duneproject testvtk`, adding `dune-grid` as
dependency.
2. Create subdirectory `dune/grid/io/file/test/` in `testvtk`
3. Copy the file
** Also affects: dune-grid (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2058415
Title:
Reading binary data in paraview broken by libexpat1
Here's a corresponding bug report for debian sid:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064762
** Bug watch added: Debian Bug tracker #1064762
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064762
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Summary changed:
- Reading binary date broken by libexpat1 update
+ Reading binary data in paraview broken by libexpat1 update
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2058415
Title:
This problem looks related and has been reported for arch:
https://discourse.paraview.org/t/i-cannot-read-a-vtp-file-i-could-open-
yesterday-can-someone-try-to-open-it/13938
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
The recent update of libexpat1 to version 2.5.0-2ubuntu0.1 broke Paraview.
In particular reading vtu files containing binary data fails since this update.
When trying to open files that worked fine before, Paraview now reports a
parsing error like this one:
ERROR: In
The mainline kernel indeed seems to fix the issue: Not a single failed
suspend/resume cycle since using 4.19.1.
** Tags added: kernel-fixed-upstream
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Yes the issue did not happen prior to the update to 18.04. But I don't
know if there was a prior kernel in 18.04 where the issue did not occur,
because it's not happening 100% of the time. Still a successful resume
is rare.
I'll give the mainline kernel a try.
--
You received this bug
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1801743/+attachment/5209384/+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/1801743
Title:
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1801743/+attachment/5209390/+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/1801743
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1801743/+attachment/5209388/+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/1801743
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1801743/+attachment/5209381/+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/1801743
Title:
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1801743/+attachment/5209392/+files/RfKill.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1801743
Title:
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1801743/+attachment/5209382/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1801743/+attachment/5209391/+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/1801743
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1801743/+attachment/5209389/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1801743/+attachment/5209387/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1801743/+attachment/5209394/+files/WifiSyslog.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs,
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1801743/+attachment/5209385/+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/1801743
Title:
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1801743/+attachment/5209393/+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/1801743
Title:
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1801743/+attachment/5209386/+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/1801743
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1801743/+attachment/5209383/+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/1801743
apport information
** Tags added: apport-collected
** Description changed:
After upgrading to kubuntu 18.04 resuming from suspend fails in most
cases on my laptop. When trying to resume the power LED is turned on,
but the screen stays black and the system does not respond at all.
Thanks for the information. I just filed bug #1801743.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774950
Title:
Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and
Kubuntu
Public bug reported:
After upgrading to kubuntu 18.04 resuming from suspend fails in most
cases on my laptop. When trying to resume the power LED is turned on,
but the screen stays black and the system does not respond at all.
Switching to another virtual terminal is not possible and closing the
So should I file a new bug report or should the status of this one be
changed again?
Can I help by providing more information?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774950
Title:
Suspend
My Dell Latitude e7440 (core i7 4600U, intel graphics) shows a similar
behaviour after updating to 18.04:
Wake-up after suspend often fails with power LED on. Hard shut down
seems to be the only way to recover. Sometimes, additionally to this,
suspend seems to incomplete in the sense that the
Since I stumbled about this again: The following minor changes would
increase usability of forms a lot since they make the behaviour of
Okular more transparent.
a) Add a menu entry "save form data" that makes Okular store the data in the
file itself.
b) When the user tries to close a filled in
(In reply to Yuri from comment #43)
> (In reply to Carsten Gräser from comment #42)
> > Yuri, this is not correct. Okular can in principle save the data to the pdf.
> > But the interplay of this with saving to and loading from .kde/... is not
> > very intuitive.
>
Yuri, this is not correct. Okular can in principle save the data to the
pdf. But the interplay of this with saving to and loading from .kde/...
is not very intuitive.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
I also stumbled about the fact that it seems to be impossible to have
multiple instances of the same filled in form under the same file name
and got the impression that "Save as..." does not work. After some
experimenting I found out the problem with "Save as...":
There's two places where form
Now, without glidepoint daemon, I can adjust the speed and acceleration
for the touchpad in KDEs touchpad config dialog.
The only (small) remaining problem is that scrollong is much faster now
with the touchpad and I can't find a way to adjust this properly.
--
You received this bug
Stopping and restarting the service 'glidepoint' also reactives the
touchpad temporarily. So I use
sudo service glidepoint stop; sudo service glidepoint start
as a work around. As the touchpad is disfunctional again after a few
minutes, this is really annoying.
Perhaps this means that this
I just noticed that the glidepoint package came preinstalled with my
notebook (on ubunu 12.04, as far as I remember).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1382865
Title:
Dell Latitude
After removing the preinstalled glidepoint package and rebooting the
problem seems to be gone. As a nice side effect the touchpad now appears
in the default config dialoge.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I seem to have the same problem on a Dell Latitude e7440 since the
update to 14.10. After some time the touchpad and the trackpoint stop
working, i.e., the mouse cursor is frozen and there's no reaction to
clicks. Similar to the reporter Xorg.0.log contains the following error:
[...]
(EE)
Also effects me. However it does not happen on any resize. But I
observed the following (only for konsole windows):
* maximazing horizontally or vertically using a hotkey sometimes triggers a
freeze
* changing the size using 'wmctrl' sometimes triggers a freeze
* the whole desktop flickers on
I can't reproduce the bug in 9.10 anymore. Regarding
http://bugs.gentoo.org/133612 it seems to be an upstream bug. Seems to
be fixed in vim-7.2.
However I could not find a corresponding bug report/patch on the vim-dev
list.
--
External command are broken in gvim started from menu
Same problem in 9.10. Will this ever be fixed?
** Also affects: libcairo (Ubuntu)
Importance: Undecided
Status: New
--
some ~/.fonts.conf settings do no override desktop-wide gnome settings (hinting
style)
https://bugs.launchpad.net/bugs/161058
You received this bug notification
Same problem here since the karmic upgrade on a dell latitude d630
--
touchpad creates noise in headphones
https://bugs.launchpad.net/bugs/457710
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I observe the same problem im 9.04. I mainly use kde which respects the
per font setting of hintstyle in .fonts.conf . However any gnome app
(e.g. gvim, gnome-terminal) ignores it.
--
some ~/.fonts.conf settings do no override desktop-wide gnome settings (hinting
style)
Please also update the nvidia-glx-180 package in intrepid to solve the
suspend issue.
--
update request: nVidia ver 180.27, pre-release
https://bugs.launchpad.net/bugs/322416
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Any hope that 180.11 is updated to 180.25 soon in the 8.10 repositories
?
By the way, I can't see any hint that 180.25 is beta in the announcement.
Perhaps
http://www.nvidia.com/object/unix.html
is simply not up-to-date.
--
nvidia 180.* driver inhibits resume from suspend
Public bug reported:
In ubuntu 8.10 /usr/share/applications/gvim.desktop contains the line
'Exec=gvim -f %F'. This prevents from executing external commands in
background if gvim is started from menu.
For example ':!xterm ' does not work.
If the '-f' option is omitted everything works as
44 matches
Mail list logo
