Still happens on my Lenovo Thinkpad P50.
When shutting down, I have to hold down the power button for five
seconds to get it to shut down completely, even though the external red
LED (the dot of the "i" in "Thinkpad" on the lid) has turned off.
I cannot restart the machine, same story as when
Still happens on my Lenovo Thinkpad P50.
When shutting down, I have to hold down the power button for five
seconds to get it to shut down completely, even though the external red
LED (the dot of the "i" in "Thinkpad" on the lid) has turned off.
I cannot restart the machine, same story as when
Some issue on 24.04:
root@noble ~ # curl -s https://launchpadlibrarian.net/250515419/test.html |
html2text; echo $?
Input recoding failed due to invalid input sequence. Unconverted part of text
follows.
“Test�?)
0
--
You received this bug notification because you are a member of Ubuntu
Public bug reported:
I ran "sudo apt install diffuse" and expected diffuse to be installed and
working.
However, diffuse was installed but not working.
When running diffuse from command-line, I noticed it was missing "distutils".
Manual installation of python3-distutils-extra solved the
Hello,
which Info are you waiting for?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1548206
Title:
Kate spellcheck not working
To manage notifications about this bug go to:
root# find / -iname *hspell*
find: ‘/run/user/1000/doc’: Permission denied
/usr/lib/x86_64-linux-gnu/enchant-2/enchant_hspell.so
/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/sonnet/sonnet_hspell.so
/snap/gnome-3-28-1804/161/usr/lib/x86_64-linux-gnu/enchant/libenchant_hspell.so
This is all.
--
You
Hello Waqar,
at least I do not have an "hspell" package installed. Maybe it comes in
another package name? Here are all installed packages with "spell" in
their name or description title:
$ dpkg -l | grep spell
ii aspell0.60.8-3
Operating System: Kubuntu 21.10
KDE Plasma Version: 5.23.4
KDE Frameworks Version: 5.89.0
Qt Version: 5.15.2
Kernel Version: 5.13.0-22-generic (64-bit)
Graphics Platform: X11
I still get the warning when starting e.g. kwrite
Hspell: can't open /usr/share/hspell/hebrew.wgz.sizes.
It seems this version string was introduced in a upstream Debian patch
indeed, when it was based on a prerelease version of Python 3.9. The
patch (git-updates.diff) was dropped later.
Introduced (erroneously):
This also took Docker down on 18.04 with the update for USN-4653-1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1870514
Title:
update containerd:amd64 1.3.3-0 stops docker daemon
To manage
Public bug reported:
I was busy filling out my persona details just after I chose ZFS for the
HD.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.15.2
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
ApportVersion:
As a new chromium version came in I have tested this again:
gert@flupp:~$ rm -rf ~/snap/chromium/current/.config/
gert@flupp:~$ chromium
[10090:10090:1109/162748.523398:ERROR:sandbox_linux.cc(369)]
InitializeSandbox() called with multiple threads in process gpu-process.
[10090:10090:1109
After creating the Symlink inside of the .config/chromium/ directory, my
config was transfered fine on the next chromium restart. So I have found
a workaround for my situation. Thank you.
gert@flupp:~/.config/chromium$ ln -s Profile\ 1/ Default
gert@flupp:~/.config/chromium$ cd
gert@flupp:~$ rm
Hello Olivier, please see the end of my last comment #22.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849693
Title:
[snap] Upgrading from kubuntu 19.04 to 19.10 lost all chromium
settings
To
After starting the PC and logging into KDE without starting chromium:
gert@flupp:~$ snap connections chromium | grep password
password-manager-service chromium:password-manager-service
:password-manager-service manual
I remember that after the upgrade when the configs have not been
apport information
** Attachment added: "Snap.Info.chromium.txt"
https://bugs.launchpad.net/bugs/1849693/+attachment/5299959/+files/Snap.Info.chromium.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/1849693/+attachment/5299953/+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: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1849693/+attachment/5299952/+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/1849693
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1849693/+attachment/5299956/+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/1849693
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1849693/+attachment/5299949/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1849693/+attachment/5299950/+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/1849693
Title:
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1849693/+attachment/5299951/+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/1849693
Title:
apport information
** Attachment added: "Snap.Info.core18.txt"
https://bugs.launchpad.net/bugs/1849693/+attachment/5299961/+files/Snap.Info.core18.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "Snap.Info.gtk-common-themes.txt"
https://bugs.launchpad.net/bugs/1849693/+attachment/5299962/+files/Snap.Info.gtk-common-themes.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1849693/+attachment/5299963/+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/1849693
Title:
apport information
** Attachment added: "Snap.Connections.txt"
https://bugs.launchpad.net/bugs/1849693/+attachment/5299958/+files/Snap.Connections.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1849693/+attachment/5299954/+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/1849693
apport information
** Attachment added: "Snap.Info.core.txt"
https://bugs.launchpad.net/bugs/1849693/+attachment/5299960/+files/Snap.Info.core.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "Snap.ChromiumPrefs.txt"
https://bugs.launchpad.net/bugs/1849693/+attachment/5299957/+files/Snap.ChromiumPrefs.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1849693/+attachment/5299955/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Will the transfer of the .config/chromium files start again when
removing the snap/chromium files? So I could test if it works with a
second try.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849693
apport information
** Tags added: apport-collected eoan snap
** Description changed:
I just have upgraded from kubuntu 19.04 to 19.10. chromium was changed
from deb to snap 77.0.3865.120-0ubuntu1~snap1. When starting the browser
for the first time, it should have imported all former
Hello Olivier,
No, I don't think that chromium was installed as snap before. I have
never installed snap things myself, only maybe such packages that were
installed by the system, AFAIK.
I did the apport-collect and attached the history.log
Regards
Gert
** Attachment added: "histor
Public bug reported:
I just have upgraded from kubuntu 19.04 to 19.10. chromium was changed
from deb to snap 77.0.3865.120-0ubuntu1~snap1. When starting the browser
for the first time, it should have imported all former settings. But it
did not. E.g. all bookmarks and saved passwords are gone.
Public bug reported:
Disabling repos under Other Software usually doesn't open up the
password window like it should. The window just turns grey but I can use
it when I click on it as if nothing happened.
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: software-properties-gtk 0.97.11
Public bug reported:
After adding a new domain with MDomain and rebooting apache2, apache2
crashes:
$ dmesg
...
apache2[1241]: segfault at 0 ip 7f288669a86d sp 7ffc76b935a0 error 4
in mod_md.so.0.0.0[7f2886682000+31000]
Updating mod_md to 1.1.17 would solve it:
I am currently using Debian 10 Buster with Wayland.
This problem is not existing anymore at this release.
Wayland no longer uses an extra fence register if dual monitor is used.
The wrong reservation of fence registers at intel_blit.c still exists, but does
not harm, because the limit of 14
Unfortunatelu no new flavor of Ubuntu is supporting 32 bits anymore.
Therefore I had to install Debian 10 (Buster).
Wayland at Debian is running without severe problems.
This problem also is not existing anymore, because Wyland is no longer using an
extra fence register if a dual monitor is
That code path fails to detect that neither --wait or -w is supported, since
iptables-restore returns a successful return code on invalid parameters and
firewalld uses the return code to detect whether it works:
# echo "#foo" | /sbin/iptables-restore --wadit=2; echo $?
/sbin/iptables-restore:
Public bug reported:
firewalld from Ubuntu 18.04 LTS sometimes attempts to use the `--wait`
option to iptables-restore, which is only valid on iptables 1.8.x and
newer and not on 1.6.1, as bundled with bionic. (At least according to
the man page, the comments in the firewalld code implies that it
Mostly when firewalld fails with that error, a restart will fix it (It
seems to only hit that code path sometimes), however if it is a headless
box, that restart might be tricky.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I experienced the same problem when I tried to install Ubuntu 19.04 with
the initial option to install third party drivers. After installation
and the first reboot, the system will not start up. I will see if I can
reproduce this and post the log report.
I have a Dell Vostro 3670 PC with the
I have not tried running SDDM rather than the normal Ubuntu Desktop.
Will try that tomorrow.
I still get the same error with Ubuntu 19.04 when I try to install the
Nvidia driver. Anyone with a solution?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I have a NVIDIA Corporation GP107 [GeForce GTX 1050] card and ubuntu 19.04
installed. After installing the lastest Nvidia driver-430, the dektop GUI is
lost when you reboot (18.10 gave the same issue). I tried many proposed
solutions, including the one above. Nothing worked.
I finally found a
I did at #14 again, set verification-done-bionic for this fix, as requested.
Again it disappears.
I now tested the fix 3 times (once for cosmic and twice for bionic).
This time I did the same test as at #8.
Whatever you do it was the last time I test this bug.
--
You received this bug
Problem could not be reproduced, because it was hidden by bug #1795774.
After installation from proposed, the problem was solved:
root@gert-laptop:/etc/apt# dpkg -s libmutter-2-0 | grep Version
Version: 3.28.3+git20190124-0ubuntu18.04.2
--
You received this bug notification because you
Problem reproduced with old version:
gert@gert-laptop:~$ dpkg -s libmutter-2-0 | grep Version
Version: 3.28.3-2~ubuntu18.04.2
Apr 19 14:41:11 gert-laptop gnome-shell[991]: CoglError set over the top of a
previous CoglError or uninitialized memory
To reproduce the problem at bionic I had to uninstall the cryptsetup-package
and use DeviceTimeout 1 at /etc/plymouth/plymouthd.cfg.
After installing plymouth:i386 0.9.3-1ubuntu7.18.04.2, the problem disappeared.
Problem solved.
--
You received this bug notification because you are a member of
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794292
Title:
plymouthd crashed with SIGSEGV in /sbin/plymouthd:11
Installed packages plymouth and libplymouth4 from cosmic-proposed.
e.g: Get:1 http://archive.ubuntu.com/ubuntu cosmic-proposed/main i386 plymouth
i386 0.9.3-1ubuntu10.1
To test the fix I verified plymouth and drm-modules are not present at
initramfs.
This causes intel drm to be initiated after
** Tags removed: verification-needed-cosmic
** Tags added: verification-done-cosmic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794292
Title:
plymouthd crashed with SIGSEGV in /sbin/plymouthd:11
Verification succeeded. Problem solved
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1795774
Title:
gnome-shell
Verification succeeded. Problem solved.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1790525
Title:
gnome-shell
Sorry, I missed the previous request to verify at bionic.
Bionic is my basic Ubuntu.
I only use cosmic for test. At the past I installed cosmic only to verify the
wayland-patch for old Intel-graphics. This worked but I got a lot of other
problems with unstable starting of ubuntu, caused by
Created attachment 143414
fix intel_blit.c
fix error_patch2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1797882
Title:
At dual monitor intel_do_flush_locked failed: Resource deadlock
avoided
Created attachment 143415
libdrm_ignore_deadlock
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1797882
Title:
At dual monitor intel_do_flush_locked failed: Resource deadlock
avoided
To manage
Some more investigation, understanding and adding 2 other possible fixes for
the problem.
The problem occurs at Ubuntu 18.10 only at gdm3 with wayland using dual monitor.
It is not occuring with wayland at single monitor.
It totally doesnot occur if gdm3 is not using wayland.
At ubuntu 18.04 the
** Tags added: cosmic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1790525
Title:
gnome-shell assert failure: double free or corruption (fasttop) in
g_free() from g_error_free() from
Reinstalled current libmutter.
With dual monitor horizontal aside this problem could not be reproduced because
logon-session crashes before showing logon-screen, (caused by bug #1790525).
Installed proposed version:
apt list libmutter-3-0
Listing... Done
libmutter-3-0/cosmic-proposed,now
** Tags removed: cosmic verification-needed-cosmic
** Tags added: verification-done-cosmic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1790525
Title:
gnome-shell assert failure: double free or
Reinstalled current libmutter.
With dual monitor horizontal aside this gives
Feb 1 22:26:58 Gert2 gnome-shell[1038]: Failed to allocate texture: Failed to
create texture 2d due to size/format constraints
Feb 1 22:26:58 Gert2 gnome-shell[1038]: CoglError set over the top of a
previous
Issue https://gitlab.gnome.org/GNOME/mutter/issues/453 is added to
mutter
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1795760
Title:
Xwayland crashed with SIGABRT in OsAbort() from ... from
Because this bug no longer is marked as duplicate of #1745799, I now add
the bug-fix (tested by me for a long time) to this bug.
** Attachment added: "Patch"
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1795760/+attachment/5231631/+files/error9_patch.txt
--
You received this
I created bug #1795760, which describes a Xwayland-abort and got the
status duplicate of 1745799.
Below is a part of the symbolic trace of the abort.
#7 0x004b6296 in xwl_log_handler (format=0xb7dc71ea "%s@%u: error %d: %s\n",
args=0xbf9c7994 "\027uܷ\255\001") at
Wow, probably not. The ticket stems from 2015.
As far as I am concerned this ticket may be closed.
I'm not sure if I acted correctly, but I changed the status to Fix
Released (as I don't see an option for 'Close'.
** Changed in: needrestart (Ubuntu)
Status: Incomplete => Fix Released
--
Mesa-bug:
https://bugs.freedesktop.org/show_bug.cgi?id=109102
** Bug watch added: freedesktop.org Bugzilla #109102
https://bugs.freedesktop.org/show_bug.cgi?id=109102
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Without solving this problem, wayland cannot be used after logon, when
using dual monitor. The sesssion stops very easy and often. Work is
lost; you have to logon again. E.g. the simple switching between 2
overlapping windows causes the end of the session.
I changed
Trace
** Attachment added: "trace at forced coredump"
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1797882/+attachment/5223254/+files/wayland_stacktrace.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 1745799 ***
https://bugs.launchpad.net/bugs/1745799
This is not a duplicate. It is a crash at OsAbort, but that is the only
coincidence with #1745799.
The cause is different.
It contains a working solution.
PLease do something with it and do not mark it as
Mathieu,
I have to decline. I do not think the Ubuntu-world is waiting for my
newbie Mail-address.
Gert
On 12/6/18 5:25 PM, Mathieu Trudel-Lapierre wrote:
> Sorry, we don't see it there. The emails are re-jiggled by Launchpad.
>
> If you prefer, you can send it to me directly (
Hello Mathieu,
I hope you can see the sender mail-address.
Thanks for your cooperation.
It is nice to be able to contribute a little bit to Ubuntu/Linux.
Gert
On 12/4/18 8:43 PM, Mathieu Trudel-Lapierre wrote:
> Gert, could you provide us with an email address so we can correctly
> att
.
The command systemd-inhibit --list shows next entry as soon as an external
monitor is attached to the laptop.
Who: gert (UID 1000/gert, PID 2342/gsd-power)
What: handle-lid-switch
Why: Multiple displays attached
Mode: block
So program gsd-power is responsible for inhibiting
Sorry, previous information wrong.
At upgraded 18.04 I have cryptsetup and crypsetup-bin, not cryptsetup-initramfs.
At fresh 18.10 I have no package from cryptsetup.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
No.
I have cryptsetup and crypsetup-bin, not cryptsetup-initramfs.
For checking a fix for gnome-wayland I did a fresh install of 32-bits 18.10
from a "mini" (because no image available for 32-bits).
Apparently this does not automatically install cryptsetup-initramfs.
It is rather strange,
The patch I described before solves the problem, but for some reason plymouth
does not attach the second renderer to the keyboard. Therefore switching to
text-mode by pressing escape-key does not work.
To make this work variable manager->local_console_managed must be set to false.
This causes
I do not have access to upstream and also have no idea what to add
there.
I have the impression the root cause of the plymouth crash is a configuration
problem.
I compared Ubuntu 18.04, upgraded from 16.04, with the fresh install of 18.10.
At 18.10 file
I do not have access to upstream and also have no idea what to add
there.
I have the impression the root cause of the plymouth crash is a configuration
problem.
I compared Ubuntu 18.04, upgraded from 16.04, with the fresh install of 18.10.
At 18.10 file
This change seems to be reverted somehow!?
Briefly saw 0.40.x, installed the update, now the latest in repositories
is 0.36.3:
$ apt policy netplan.io
netplan.io:
Installed: 0.40.1~18.04.2
Candidate: 0.40.1~18.04.2
Version table:
*** 0.40.1~18.04.2 100
100
Same problem as described before.
To force I use timeout 1 and theme fade-in. But same problem also occurred at
my PC with the default timeout 5, as was on the trace.
I will upload the crashdump (which by default was ignored by apport).
Routine ply_renderer_free does a hard free of renderer. So
I think, I still get old stuff from 15-10
gert@Gert2:/var/cache/apt/archives$ dpkg -c
libplymouth4_0.9.3-1ubuntu11~mtrudel4_i386.deb
drwxr-xr-x root/root 0 2018-10-15 16:36 ./
drwxr-xr-x root/root 0 2018-10-15 16:36 ./lib/
drwxr-xr-x root/root 0 2018-10-15 16:36 ./lib
Problem not solved.
I think I got 4 problems:
1)
I think the second ppa (*mtrudel2*) has exacly same contents as the first one.
At least the binaries and shared loadlibraries have the same time stamp (15
october).
So this will not contain the last version.
2)
I have the idea the shared
*** This bug is a duplicate of bug 1745799 ***
https://bugs.launchpad.net/bugs/1745799
As stated above this bug report is not a duplicate and contains working code to
solve the bug.
Using this code doesn ot give any risk to the main stream of the code, it only
handles an exception.
I
Proposing next improved code
At src/libply-splash-core/ply-device-manager.c
1) at
create_devices_for_subsystem (ply_device_manager_t *manager,
const char *subsystem)
change
found_device = create_devices_for_udev_device (manager, device);
into
Wow, you replied to a report from 2015. ;)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1450763
Title:
Syntax error: ")" unexpected
To manage notifications about this bug go to:
Public bug reported:
When I click on an application tile that is above the horizontal center
line of the window in one of the category views it kicks the scrolling
up to some point. Clicking a tile again will not kick the scroll up a
second time.
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Public bug reported:
Ubuntu Software back button generally does not operate.
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: ubuntu-software 3.30.2-0ubuntu5
ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
Uname: Linux 4.18.0-10-generic x86_64
NonfreeKernelModules: nvidia_modeset
Unfortunately again it crashes, logging on with gdm3, both with and
without wayland.
The crash seems to be at the same place.
Syslog:
Oct 16 16:04:13 Gert2 systemd[1]: plymouth-start.service: Main process exited,
code=dumped, status=11/SEGV
Oct 16 16:04:13 Gert2 gdm3[710]: error: unexpectedly
** Description changed:
Using ubuntu wayland with dual monitors, configured above each other.
Dock is configured at both displays, not hiding.
Icons for "terminal" and "libreofffice Writer" are present at the dock.
Start terminal on primary screen by mouseclick on dock.
Start
Public bug reported:
Using ubuntu wayland with dual monitors, configured above each other.
Dock is configured at both displays, not hiding.
Icons for "terminal" and "libreofffice Writer" are present at the dock.
Start terminal on primary screen by mouseclick on dock.
Start libreoffice Writer on
*** This bug is a duplicate of bug 1745799 ***
https://bugs.launchpad.net/bugs/1745799
Sorry,
Code was not quite complete.
It misses freeing the error.
New version:
texture = COGL_TEXTURE (cogl_texture_2d_new_from_bitmap (bitmap));
cogl_texture_set_components (COGL_TEXTURE (texture),
*** This bug is a duplicate of bug 1745799 ***
https://bugs.launchpad.net/bugs/1745799
I do not think this is a duplicate of bug #1745799.
At this comment I will try to give a code to solve this bug.
My symbol Xwaylnd-crash shows the next trace:
#6 0x0062b600 in FatalError (f=0x63704e
Problem can be solved at update_fbo() within clutter/clutter/clutter-
offscreen-effect.c
In this case at update_fbo a texture should be alocated with width 2560 which
is greater than maximal size 2048 of graphics cards.
Offscreen-effect does not support sliced textures, so this is impossible
At my laptop it happens at (almost) every start.
FYI I attach a symbolic trace
** Attachment added: "symbolic trace of crash after released fix"
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1794292/+attachment/5197512/+files/stack1.txt
--
You received this bug notification
Unfortunately the fix does not solve the problem and still crashes.
ProblemType: Crash
Architecture: i386
Date: Thu Oct 4 16:54:33 2018
DistroRelease: Ubuntu 18.10
ExecutablePath: /sbin/plymouthd
ExecutableTimestamp: 1538408760
MachineType: Dell Inc. Latitude D620
Package: plymouth
** Package changed: evince (Ubuntu) => gnome-shell (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1795089
Title:
Gnome-shell crashes if dual monitor connected
To manage notifications about
Public bug reported:
THis contains a fresh install of Ubuntu 18.10 to verify the solution at bug
1727356, for Intel-graphic-cards,
which do not support OpenGL 2.1 or higher.
This solution works.
A fresh install does not contain any monitors.xml file, to describe the dual
Proposed solution:
As the stacktrace below shows the problem is caused by module
cogl_texture_new_with_size at cogl/cogl/deprecated/cogl/auto-texture.c .
This module is trying to create a texture with size 2560 x 1024, which is by
default is configured by gdm3 with wayland for 2 monitors.
This
Extra info:
1.The syslog at a crash shows next error. Probably memory management at an
errormemssage is not correct. Also look at the size 2560 x 1024
Sep 08 00:18:35 Gert2 gnome-shell[2141]: CoglError set over the top of a
previous CoglError or uninitialized memory.
repainted with and without the second
monitor and the display of the external monitor contains some extra info
from the laptop-screen.
But I can logon!!!
Also I got 2 crashes on gnome-shell, but cannot reproduce.
I will add comment to 1727356 as soon as I know more.
Gert
On 08/21/2018 04:04
the problem was caused by the error at syslog:
Aug 19 23:34:11 gert-laptop org.gnome.Shell.desktop[959]: glamor: EGL version
1.4 (DRI2):
Aug 19 23:34:11 gert-laptop org.gnome.Shell.desktop[959]: Require OpenGL
version 2.1 or later.
Aug 19 23:34:11 gert-laptop org.gnome.Shell.desktop[959]: Failed
1 - 100 of 825 matches
Mail list logo
