Erkin you have the same issue I had
`/etc/ld.so.conf.d/`
should have a amdgpu conf that includes the externally packaged libs and
apparently this config slipped through the testing.
You can either uninstall the amdgpu-dkms stuff and the libs or just delete the
conf file that makes the dynamic
Ok solved it, the issue was the optional and driver, it had installed
libraries in /opt and ld was preferring them..
Removed the ld.conf entries and rebooted.
All is good now.
`ld /usr/bin/mutter | grep drm`
Gave me the hint.
--
You received this bug notification because you are a member of
Same here, stuck on upgraded system...
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2060391
Title:
gnome desktop cannot start as mutter fails to find drmModeCloseFB
Status in
This issue never happened to me with my 3x FHD setup at work, but now I
am working from home with 2x 4K and 1x FHD and I am getting constant
corruptions.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
And another correction
sudo apt install mutter/mantic-proposed
and
sudo apt install -t mantic-proposed mutter
do different things :-)
the mutter fix works :-)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
Ok correction: on a colleagues machine the issue occurs when his laptop is
detached from the dock (external monitors) on my machine it occurs even when
docked.
the `MUTTER_DEBUG_KMS_THREAD_TYPE=user` fix/workaround works though.
--
You received this bug notification because you are a member of
For me the new mutter does not fix the issue, gnome-shell does still
crash/get killed when I lock my screen.
2 other people at my office have NO ISSUES at all, despite both being on the
stable release and also having AMDGPU devices (one is the exact same device I
have).
Thinkpad P14s G2a
--
I would say this is still unfixed, I still have this issue on 20.10 and
21.04
** Attachment added: "Screenshot from 2021-03-11 23-45-23.png"
https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/1179524/+attachment/5475936/+files/Screenshot%20from%202021-03-11%2023-45-23.png
** Changed in:
I guess we can close this issue, it has ben fixed in the 20.04 release
of ubuntu :-)
** Changed in: nautilus (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
Public bug reported:
When I connect to my desktop PC via remmina all colors a broken.
Using MS RD Client on Android gives me no issues at all.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: remmina 1.4.2+dfsg-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux
name DOOMELITE.
Using workgroup WORKGROUP.
smb: do_mount - URI = smb://openwrt/doom
smb: do_mount - try #0
smbc_stat(smb://openwrt/doom)
smb: auth_callback - kerberos pass
smb: auth_callback - out: last_user = 'doommaster', last_domain = 'WORKGROUP'
SMBC_server: server_n=[openwrt
dsdb_group_audit: 10
dsdb_group_json_audit: 10
Using netbios name DOOMELITE.
Using workgroup WORKGROUP.
smb: do_mount - URI = smb://openwrt/doom
smb: do_mount - try #0
smbc_stat(smb://openwrt/doom)
smb: auth_callback - kerberos pass
smb: auth_callback - out: last_user = 'doommaster
: last_user = 'doommaster', last_domain = 'WORKGROUP'
SMBC_server: server_n=[openwrt] server=[openwrt]
-> server_n=[openwrt] server=[openwrt]
Opening cache file at /run/samba/gencache.tdb
tdb(/run/samba/gencache.tdb): tdb_open_ex: could not open file
/run/samba/gencache.tdb: Permission den
I created a bug report on the gnome project…
for reference https://gitlab.gnome.org/GNOME/nautilus/issues/1240
** Bug watch added: gitlab.gnome.org/GNOME/nautilus/issues #1240
https://gitlab.gnome.org/GNOME/nautilus/issues/1240
--
You received this bug notification because you are a member
I made a short clip of it…
the folder it displays in between is not even on the level up, but a completely
different previously displayed folder.
** Attachment added: "Screencast from 03.10.2019 11:29:21.webm"
Public bug reported:
When entering a folder in nautilus and deleting a file permanently
"shift+del" the selection jumps and sometimes even the previous folder
level is being displayed.
This is super confusing.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: nautilus 1:3.34.0-1ubuntu1
I am also affected, same solution as for other, I simply need to
reconnect from the UI.
The same headset works fine on Android, Windows, Mac OS, iOS and even my
cheap DAB-Receiver can stream to it via A2DP right away.
For me the issue exists since 18.4 and is still present in 18.10.
I am using
this is still broken…
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-online-accounts in Ubuntu.
https://bugs.launchpad.net/bugs/1733002
Title:
Google Online Account Two Factor with hardware key fails immediately
Status in
ome.SettingsDaemon.MediaKeys.desktop[14428]: #
watch_established: "/org/gnome/terminal/legacy/" (establishing: 0)
Mär 30 01:17:54 gsd-media-keys[14428]: Failed to set new screen percentage:
Timeout was reached
Mär 30 01:17:54 gsd-media-keys[14428]: Failed to set new screen percentage:
als also still experiencing this behaviour
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1427877
Title:
Media, brightness and volume keys don't work with GNOME 3.15.90
28]: Failed to set new screen percentage:
Timeout was reached
Mär 30 01:17:54 gsd-media-keys[14428]: Failed to set new screen percentage:
Timeout was reached
Mär 30 01:17:55 pkexec[845]: pam_unix(polkit-1:session): session opened for
user root by (uid=1000)
Mär 30 01:17:55 pkexec[845]: do
MediaKeys.desktop[14428]: #
watch_established: "/org/gnome/terminal/legacy/" (establishing: 0)
Mär 30 01:17:54 gsd-media-keys[14428]: Failed to set new screen percentage:
Timeout was reached
Mär 30 01:17:54 gsd-media-keys[14428]: Failed to set new screen percentage:
Timeout was reached
M
Public bug reported:
When I view a certain folder in Nautilus it first gets very very slow
and then crashes with a segfault:
nautilus[25623]: segfault at 7faa989aec13 ip 7fac52b59dd0 sp
7fac2c13b6e8 error 4 in
libgdk_pixbuf-2.0.so.0.3000.7[7fac52b46000+1f000]
(nautilus:25779):
crashdump
** Attachment added: _usr_bin_nautilus.1000.crash
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1363003/+attachment/4189929/+files/_usr_bin_nautilus.1000.crash
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
apport information
** Attachment added: usr_lib_nautilus.txt
https://bugs.launchpad.net/bugs/1363003/+attachment/4189938/+files/usr_lib_nautilus.txt
** Attachment removed: _usr_bin_nautilus.1000.crash
apport information
** Attachment added: ProcEnviron.txt
https://bugs.launchpad.net/bugs/1363003/+attachment/4189937/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
apport information
** Tags added: apport-collected trusty
** Description changed:
When I view a certain folder in Nautilus it first gets very very slow
and then crashes with a segfault:
nautilus[25623]: segfault at 7faa989aec13 ip 7fac52b59dd0 sp
7fac2c13b6e8 error 4 in
** Attachment added: error log
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1041790/+attachment/4147886/+files/error3.gz
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
*** This bug is a duplicate of bug 215802 ***
https://bugs.launchpad.net/bugs/215802
it is funny or sad :) that this bug still persists :(
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lynx in Ubuntu.
29 matches
Mail list logo
