Public bug reported:
The touchpad of my laptop is suddenly not being detected. After inputing
'xinput list' on terminal, the touchpad isn't showing up.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.8.0-53-generic 5.8.0-53.60~20.04.1
ProcVersionSignature: Ubuntu
This pretty much makes xfce4 unusable in headless install of 20.04.2
LTS.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860921
Title:
Missing window decorations in VNC
To manage notifications
I don't know much about xHCI so Mathias can comment on that. I do
remember seeing messages like:
usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
in the past but not sure if it is only with ICL. It is also weird that
the TCSS xHCI is doing anything if you plug TBT 3 device since USB
>Which CPU models are still failing with
>5.3.0-52.46 or 5.3.0-52.46+lp1861395v1?
i7-9700k is failing..
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872001
Title:
5.3.0-46-generic - i915 -
Hi all,
It seems the problem is related to the guest session wrapper
(/usr/lib/lightdm/lightdm-guest-session). As a workaround, it is possible to
disable this wrapper removing the file
/usr/share/lightdm/lightdm.conf.d/50-guest-wrapper.conf
--
You received this bug notification because you
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872001/comments/72
- Freezes still seen.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872001/comments/101
- 5.3.0-52-generic --> Freeze not seend, but this is causing crashes (log file
added)
** Attachment added:
Thanks,
This problem occurs with my workstation --> I will try this on monday and
I will share feedback.
Br,
Mika
pe 1. toukok. 2020 klo 0.00 Francis Ginther
kirjoitti:
> This is a likely duplicate of LP:#1872001. You can try installing the
> test kernel mentioned in
Possible duplicate bug to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872001
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875862
Title:
Display freeze quite often
To manage
Reproduced also with 5.3.0-51-generic.
>uname -a
Linux tower 5.3.0-51-generic #44~18.04.2-Ubuntu SMP Thu Apr 23 14:27:18 UTC
2020 x86_64 x86_64 x86_64 GNU/Linux
>dmesg | tail
[ 19.805979] audit: type=1400 audit(1588163641.170:73): apparmor="STATUS"
operation="profile_load"
sudo cat /sys/class/drm/card0/error > card0_error.txt
** Attachment added: "/sys/class/drm/card0/error content"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1875862/+attachment/5363447/+files/card0_error.txt
--
You received this bug notification because you are a member of Ubuntu
Public bug reported:
>From syslog:
Apr 29 13:41:44 tower kernel: [20711.955797] i915 :00:02.0: Resetting rcs0
for hang on rcs0
This seems to happen 1-10 times per day. Not sure is this something
related to PyCharm usage, but 80% of cases I have PyCharm in use when
display freezes. Freeze
... and I also know this workaround and it won't work if no password is
set up!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849859
Title:
smb printing fails
To manage notifications about this
This is not the best solution!
I hope that will come as soon as possible a patch!
That can not be that hard, can it???
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849859
Title:
smb printing
Despite really a lot of updates (samba, cups) the "held for
authentication" problem persists!
I hope, it's comming soon a solution. This is very disappointing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Vielen Dank dir erstmal, wenn ich mal wieder Zeit übrig habe, kann ich
ja mal auf einen anderen Desktop umstellen.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1855758
Title:
error when
I have installed a minimal server Ubuntu 20.04 mit LXQT as desktop
environment.
If you test it yourself, here are my installation command:
sudo apt-get install lxqt-core kde-window-manager intel-microcode sddm
plasma-nm qterminal
--
You received this bug notification because you are a member
Hallo Andreas, the configuration of the NAS does not allow for anything in this
aspect.
(look at the attachment).
The dbus error I have never seen that in a older Ubuntu too. Its a normal NAS
connecting to it via smb.
In the journalctl -b 0 there is no entry.
(Ich habe es paar mal versucht,
Is there a patch to be expected or do I have to do it myself?
Where should this ominous file smbspool.c be?
"find / smbspool.c" cannot find it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849859
This worked for me, many thanks.
(Ich hoffe, nach dem nächsten Update wird dieser workaround nicht auch
weggepatcht.)
But the problem with the error ( see attachment) stays on, I can click
it away, but I don't know, where it comes from.
** Attachment added: "error.bmp"
I have now reported a new bug:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1855758
But anyway I think, it belongs here.
@ Andreas Hasenbeck: Ich verstehe deinen letzten Kommentar nicht, mein
Englisch ist aber auch nicht so perfekt. Schreibst du da, es gibt eine
Lösung?
--
You
And this:
** Attachment added: "not mounted.bmp"
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1855758/+attachment/5311191/+files/not%20mounted.bmp
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Befor a while when I connect to smb server (nas) permanently appears
"Error while getting peer-to-peer dbus connection: Operation was
cancelled"
Nevertheless, it has connected.
Well, last weekend any samba packages were updated, now the connection
fails.
I think, it is
Or should I open a new bug report?
This new bug is very annoying.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849859
Title:
error when connecting to smb server
To manage notifications about
And this:
** Attachment added: "not mounted.bmp"
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1849859/+attachment/5310640/+files/not%20mounted.bmp
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Yesterday were a lot of updates in samba package and now
all is out of work, nothing goes on, nix geht mehr.
Connection to the server fails completely, that ist very bad, more then
the printer bug.
** Attachment added: "Abbruch.bmp"
In this days cups-filters, libcupsfilters1, cups-filters-core-driver,
cups-browsed and libfontembed1 was upgraded.
Since then nothing works anymore, printing per USB don't work anymore too.
Error message: Filter failed
@ Till Kamppeter
The described bug in Fedora 30 seems to be the same.
Noch als Ergänzung:
Das System ist ein Ubuntu Server 20.04 (Minimalinstallation) mit den
nachinstallierten Paketen lxqt-core kde-window-manager intel-microcode
sddm plasma-nm qterminal cups
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Besagte Datei jobviewer.py ist laut Dateiinfo ein Python-Script, installiert
ist aber Python3.
Könnte dies zu dem Fehler führen?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849859
Title:
error
Danke für die Antwort, leider fällt es mir schwer, auf Englisch zu
antworten, und erst recht einen Bug zu beschreiben.
Ich glaube dennoch, dass es sich um einen solchen handelt, weil ich die gleiche
Druckerkonfiguration wie unter 18.04 durchgeführt habe, dort aber diese
Probleme nicht hatte.
** Description changed:
when I connect to smb server (nas) permanently appears
"Error while getting peer-to-peer dbus connection: Operation was
cancelled"
The printer at this NAS doesn't work too.
"held for authentication KeyError: 'auth-info-required'"
The same printer at
Attachment
** Attachment added: "Terminal.bmp"
https://bugs.launchpad.net/ubuntu/+source/budgie-desktop/+bug/1849859/+attachment/5300129/+files/Terminal.bmp
** Package changed: budgie-desktop (Ubuntu) => samba (Ubuntu)
--
You received this bug notification because you are a member of
Attachment
** Attachment added: "print held.bmp"
https://bugs.launchpad.net/ubuntu/+source/budgie-desktop/+bug/1849859/+attachment/5300128/+files/print%20held.bmp
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
when I connect to smb server (nas) permanently appears
"Error while getting peer-to-peer dbus connection: Operation was
cancelled"
The printer at this NAS doesn't work too.
"held for authentication KeyError: 'auth-info-required'"
The same printer at usb port works fine.
BTW, did you enable any Linux specific configuration in the BIOS? For
example to enable S3 (many systems I've seen default to s2idle
nowadays).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1825395
Thanks for the logs. It seems like the BIOS does not handle S3 exit
properly and leaves the Thunderbolt host router unconfigured. I wonder
if there is a BIOS upgrade for this system and have you tried that?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Can you also attach full dmesg of the boot so that we can see the
initial PCI configuration? Now all the dmesgs are missing that
information.
When it initially works, do you boot with the dock connected or not?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
On "legacy enumeration" systems, such as this one the BIOS SMI handler
enumerates the PCI bridges before handing off to the OS. The bridges
here are the TBT host router bridges so no need for any authorization.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Hi, the BIOS is expected to configure the PCI bridges leading to the TBT
controller but it does not seem to do that:
[3.725792] pci :06:00.0: bridge configuration invalid ([bus 00-00]),
reconfiguring
[3.725799] pci :06:01.0: bridge configuration invalid ([bus 00-00]),
killall updatedb.mlocate and reboot. Seems that problem solved (for
now).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1190696
Title:
updatedb.mlocate uses 100% of the hdd IO. The OS is
Ubuntu 18.04.1 LTS, same issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1190696
Title:
updatedb.mlocate uses 100% of the hdd IO. The OS is completely
unusable.
To manage notifications
Wow, eight years gone and bug still exists. However, those audiostreams
from the card are alive and recordable.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/671026
Title:
HDSPMixer crashes with
since upgrade from 16.04 to 18.04 I have this issue.
gnome desktop on xorg
intuos CTH-480M-S
on startup tablet is in absolute mode, i have to open settings wacom
tablet -> stylus not recognised;
if just clicking on tablet tab button, the tablet switches back to the
set setting (relative).
I
Public bug reported:
sorry i don't have any details (newbie)
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: supertux-data 0.5.1-1build1
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
I have tried it: totem in lxqt works, parole in budgie works too, but totem in
budgie fails.
It is a problem from totem in budgie.
The gnome shell I have not installed, but dino99 wrote, it works.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
In journalctl -b is the same error message regarding totem.
So, now I have additionally installed lxqt and I can say, it ist definitly a
problem in budgie! Why ever.
In lxqt totem plays the video perfect.
Can you change it to budgie?
** Package changed: glib2.0 (Ubuntu) => budgie-desktop
** Changed in: gstreamer1.0 (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1760274
Title:
videos are stuttering extremely
To manage notifications
I mean "no error-messages"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1760274
Title:
videos are stuttering extremely
To manage notifications about this bug go to:
Running the video from terminal ( totem "/my_video" ) gives no errors.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1760274
Title:
videos are stuttering extremely
To manage notifications about
Why incomplete, what shall I do?
Run totem from the terminal shows "GLib-CRITICAL **: 14:23:22.871:
g_key_file_load_from_file: assertion 'file != NULL' failed"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
gstreamer1.0-vaapi is not installed,
Run totem from the terminal shows "GLib-CRITICAL **: 14:23:22.871:
g_key_file_load_from_file: assertion 'file != NULL' failed"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I hope, it will be solved until 18.04 comes out.
Otherwise I can not use it.
After installation all works fine, any update has triggered it!
** Changed in: gstreamer1.0 (Ubuntu)
Status: New => Confirmed
** Description changed:
I am using totem, stuttering are not in browser.
+ After
Public bug reported:
I am using totem, stuttering are not in browser.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libgstreamer1.0-0 1.14.0-1
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
ApportVersion: 2.20.9-0ubuntu2
Architecture:
Thanks staedtler-przyborski. (#12)
It worked for me in 18.04 with epson scanner.
I hope it stays that way.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1728012
Title:
Many 3rd party scanner
#528
Keep in mind that there are two *separate* issues:
1. Bug off-by-one bug in intel-spi driver that causes CMP bit to accidentally
set to 1. This results BIOS
being read-only. The bug was fixed by 9d63f17661e2 ("spi-nor: intel-spi: Fix
broken software sequencing
codes") in
#520, #522
Actually it matters if commit d9018976cdb6 is missing with this
particular BIOS/system because every time you boot the system, the BIOS
resets to default when it finds BCR register is changed. This is
different issue than the CMP=1 issue most of the users have reported.
This one also
#518
Hmm, you already compiled and booted the v4.15-rc7 kernel using my
instructions, right? It should have that fix so booting that kernel
should keep your BIOS working. You can remove the custom patch by
running command "git reset --hard HEAD^". Then you can rebuild and
install it.
--
You
Actually I think I know what is going on. I think the "unpatched" kernel
might miss commit d9018976cdb6 ("mfd: lpc_ich: Do not touch SPI-NOR
write protection bit on Haswell/Broadwell") and in that case the BIOS
resets to defaults each boot.
--
You received this bug notification because you are a
#514
No, this is not the same issue at all. The original "buggy" off-by-one
write never took place because the flash chip does not have that
SPI_NOR_HAS_LOCK bit set in the first place (and it was not there in
v4.13 either). So this is something else.
Christian, do you have Windows there? If
#512
But for the serial flash chip Christian has, the original kernel does
nothing as well (except read the JEDEC ID) so this issue cannot happen.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
#510
That's really weird because in your system both patched and unpatched
kernels are doing exactly the same thing (read JEDEC ID, nothing more).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
#506
Christian, I think you got the patch properly applied but based on the
output your serial flash is "s25fl064k". Looking at the table in
drivers/mtd/spi-nor/spi-nor.c:
{ "s25fl064k", INFO(0xef4017, 0, 64 * 1024, 128, SECT_4K) }
So this flash chip does not have SPI_NOR_HAS_LOCK and
This is what I typically do when I compile a custom kernel on a new
machine. You need development tools like git, gcc, gmake etc. but I
guess many distros have most of that stuff already installed. I did not
try these so there might be typos and something could be missing.
These steps should help
#493
You can build your own kernel so that you first apply the patch in the
bug description. Then boot to that custom kernel which should clear the
CMP bit from the serial flash and your BIOS should be functional again.
Let me know if you want instructions how to patch and build a custom
kernel.
#474
If you have status register 2 bit 6 set. e.g it reads 0x40 or something
like that, you can just clear that bit and the chip becomes read/write.
For more information about the status register you can find if you find
"w25q64dw" datasheet (or whatever the serial flash chip you have there).
#469
I mean you can clear that one status register bit (CMP) using dediprog
(or any other tool, or software as we do in step 8. fix) and your old
serial flash works just fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
#467
The BIOS and the chip are fine, there is only that one bit (CMP, bit 6)
set in the second status register that makes the whole chip read-only.
You can also use some external tools, like dediprog to clear the CMP bit
and the BIOS should work again. The fix in step 8. does the same in
This particular bug cannot affect Dell XPS 13 9350 as it is based on
Skylake and the intel-spi driver does not even support it.
However, in order to boot Linux I think you need at least to switch the
SATA controller to AHCI mode as described in:
Sorry about the delay but we wanted to make sure the proposed fix can
recover the two test systems we have reliably before asking others to
try it.
I've attached a patch to this bug that should fix the still affected
systems. It applies on top of v4.15-rc6 and I'll be sending it upstream
as well.
I think the reason why 4.14.x works is because of commit 9d63f17661e2
("spi-nor: intel-spi: Fix broken software sequencing codes").
The current theory is that for certain serial flashes (those
Public bug reported:
Can not upgrade from my version 16.04 to 17.04
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubuntu-release-upgrader-core 1:16.04.22
ProcVersionSignature: Ubuntu 4.4.0-92.115-generic 4.4.76
Uname: Linux 4.4.0-92-generic x86_64
NonfreeKernelModules: zfs zunicode
Thunderbolt support for PCs is included in v4.13-rc1 and later kernels.
Do you have a possibility to try the latest mainline kernel?
Note the userspace support is not yet ready so you need to authorize
device manually. See for example:https://www.kernel.org/doc/html/latest
This definitely sounds like a platform/configuration issue rather than a
driver bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1708043
Title:
Lenovo X1 Carbon Gen5 fails to resume
To manage
All of them are expected to work. Usually the default is "User
authorization".
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1708043
Title:
Lenovo X1 Carbon Gen5 fails to resume
To manage
Thanks for the information. I'll go through them.
Aaron, can you try to switch security level of your machine to the same:
Security Level - Display Port and USB
and see if the problem reproduces?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Thanks Aaron. So as expected the Thunderbolt controller is not there.
Only xHCI when USB-C device is connected.
Dean, is there something special you have connected to the machine?
Aaron, who has exactly the same machine and BIOS, can't reproduce the
issue you have reported.
--
You received this
Did you do any settings in BIOS related to Thunderbolt? Sometimes there
is an option called "Force power" which basically turns power on the
controller always. In normal cases that option should be disabled.
Also can you attach acpidump (along with the other things I requeted) of
the system to
Can you also try the attached patch? It should apply on top of
v4.13-rcX. I'm guessing ICM is not running on the Lenovo system so we
should start it but skip all the link reset things. Please post dmesg of
this test as well.
** Patch added: "Start ICM if it is not started"
Also can you attach full dmesg when you boot the system using v4.13-rcX
kernel?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1708043
Title:
Lenovo X1 Carbon Gen5 fails to resume
To manage
Dean, just that I understand this correctly. Do you have anything
connected to the Thunderbolt port?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1708043
Title:
Lenovo X1 Carbon Gen5 fails to
Ubuntu 16.04.2
Older similar bug with Debian: https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=773108
My stopmotion behaves as with Xavier, but when I plug in a usb webcam it starts
up.
A feature instead of bug?
stopmotion gives following warning: "Something wrong with the locale!"; me
Public bug reported:
Fails to install boot block claiming /etc/quik.conf doesn't reside on
/dev/sda even though root partition is /dev/sda3, because 16.04 uses
UUID to refer to partitions instead of old style /dev path.
quik version: 2.1-9.1ubuntu1
Ubuntu version: 16.04.2
Machine: G3 Silk @ 266
I'm also facing this error. I'm also getting the message like the other people:
error: RPC failed; HTTP 503 curl 22 The requested URL returned error: 503
Service Unavailable
fatal: The remote end hung up unexpectedly
I was also following the steps in the porting guide and also wanted to create a
*** This bug is a duplicate of bug 1522675 ***
https://bugs.launchpad.net/bugs/1522675
A fresh install of 16.10, the same issue. #40 + #42 worked for me (with
https://ubuntuforums.org/showthread.php?t=2347693).
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Is anyone here yet?
What is happens in this case?
Error message by the way:
mpgatofixed32 audio converter error: libmad error: bad main_data_begin
pointer
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Latest updates seem to have fixed this, I don't have any problems
anymore!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1574207
Title:
LibreOffice Writer freezes for a minute after loading a file
nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: mika 1988 F pulseaudio
/dev/snd/controlC1: mika 1988 F pulseaudio
/dev/snd/controlC2: mika 1988 F pulseaudio
Date: Sat May 7
I just noticed that this bug does not occur if I run LibreOffice as
sudo.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1574207
Title:
LibreOffice Writer freezes for a minute after loading a file
I just upgraded to 5.1.2.2. in Ubuntu 15.10
(ppa:libreoffice/libreoffice-5-1), and it works too. So the file opens
fine in Ubuntu 15.10 both with 5.0.5.2 and 5.1.2.2.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
In Ubuntu 15.10. I have LibreOffice 5.0.5.2.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1574207
Title:
LibreOffice Writer freezes for a minute after loading a file
To manage notifications about
Here is my file. Note that I changed all the letters to Xs, but that
doesn't affect the bug.
** Attachment added: "test.odt"
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1574207/+attachment/4652697/+files/test.odt
--
You received this bug notification because you are a member
(In reply to alex from comment #112)
> (In reply to Mika Kahola from comment #110)
> > (In reply to alex from comment #109)
> > > Dammit. Now this regression has made it into the LTS kernel. Are you
> > > guys
> > > kidding me? Is it not
Installing LibreOffice 5.0.5.2 didn't help, the same problem occurs. In
Ubuntu 15.10 (on the same computer) the file works fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1574207
Title:
(In reply to alex from comment #109)
> Dammit. Now this regression has made it into the LTS kernel. Are you guys
> kidding me? Is it not possible for the changes that caused this
> exceptionally annoying regression (as in my computer is now almost entirely
> unusable) to be removed from the
This also affects Ubuntu (and not only Xubuntu), if you remove the
libreoffice-gtk package (in order to avoid the bug #1574207).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1514249
Title:
** Tags added: libreoffice
** Tags removed: libreoffice
** Tags added: gtk
** Tags removed: gtk
** Tags added: gtk
** Description changed:
After loading a file (400 pages), Writer freezes for more than a minute
(see the attached screenshot). The soffice.bin process uses 50-51% of
CPU (=
** Description changed:
After loading a file (400 pages), Writer freezes for more than a minute
(see the attached screenshot). The soffice.bin process uses 100% CPU on
one processor.
When the file finally opens, the page count is first about 800, then it
falls to the correct 400
** Description changed:
After loading a file (400 pages), Writer freezes for more than a minute
(see the attached screenshot). The soffice.bin process uses 100% CPU on
one processor.
When the file finally opens, the page count is first about 800, then it
falls to the correct 400
Public bug reported:
After loading a file (400 pages), Writer freezes for more than a minute
(see the attached screenshot). The soffice.bin process uses 100% CPU on
one processor.
When the file finally opens, the page count is first about 800, then it
falls to the correct 400 pages.
The only
(In reply to nhellwege from comment #103)
> (In reply to Pavel Procopiuc from comment #102)
> > (In reply to nhellwege from comment #101)
> > > I am a bit lost in all these comments, could someone tell me what patch I
> > > can try to see if one of your patches has affect on my setup?
> >
> >
(In reply to Timo Aaltonen from comment #99)
> Has the latest patch even been sent to the list? At least I can't find it.
Indeed, the patch wasn't on the list. Now you can review it from
https://patchwork.freedesktop.org/patch/82206/
However, it seems that there are HW's out there that still
1 - 100 of 984 matches
Mail list logo
