[Desktop-packages] [Bug 2060391] Re: gnome desktop cannot start as mutter fails to find drmModeCloseFB
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 linker include the old lib. Then reboot and all should be fine. -- 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 mutter package in Ubuntu: Incomplete Bug description: mutter: symbol lookup error: /lib/x86_64-linux-gnu/libmutter-14.so.0: undefined symbol: drmModeCloseFB Package libdrm2: i 2.4.120-2 noble 500 Package libdrm2:i386: i 2.4.120-2 noble 500 Package libmutter-14-0: i 46.0-1ubuntu6 noble 500 Package mutter: i 46.0-1ubuntu6 noble 500 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2060391/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2060391] Re: gnome desktop cannot start as mutter fails to find drmModeCloseFB
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 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 mutter package in Ubuntu: Confirmed Bug description: mutter: symbol lookup error: /lib/x86_64-linux-gnu/libmutter-14.so.0: undefined symbol: drmModeCloseFB Package libdrm2: i 2.4.120-2 noble 500 Package libdrm2:i386: i 2.4.120-2 noble 500 Package libmutter-14-0: i 46.0-1ubuntu6 noble 500 Package mutter: i 46.0-1ubuntu6 noble 500 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2060391/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2060391] Re: gnome desktop cannot start as mutter fails to find drmModeCloseFB
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 mutter package in Ubuntu: Confirmed Bug description: mutter: symbol lookup error: /lib/x86_64-linux-gnu/libmutter-14.so.0: undefined symbol: drmModeCloseFB Package libdrm2: i 2.4.120-2 noble 500 Package libdrm2:i386: i 2.4.120-2 noble 500 Package libmutter-14-0: i 46.0-1ubuntu6 noble 500 Package mutter: i 46.0-1ubuntu6 noble 500 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2060391/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2038998] Re: [amdgpu] Screen artifacts/UI oddities on Wayland
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.
https://bugs.launchpad.net/bugs/2038998
Title:
[amdgpu] Screen artifacts/UI oddities on Wayland
Status in GNOME Shell:
Fix Released
Status in linux package in Ubuntu:
Confirmed
Status in mesa package in Ubuntu:
Confirmed
Bug description:
Laptop is a Lenovo ThinkPad P14s Gen 2 AMD.
Ryzen 7 PRO 5850U
with Radeon (RX Vega 8?) integrated graphics
16 GB RAM
Running Ubuntu 23.10 (GNOME) from a clean install performed October 9,
2023 from a daily-live/current .iso generated on October 4, 2023.
Wayland
Kernel 6.5.0-9-generic
* * * * *
Installed a pre-release build of Ubuntu 23.10 to my ThinkPad the other
day, was going through setting up and testing the usual programs.
Installed Steam through apt from the 'mantic' repositories. Installed
Proton 8.0 and Steam Linux Runtime 3.0 (Sniper) alongside two
compatible titles.
Screen corruption (white and grey streaks) present in-game when GNOME
UI elements appeared on-screen (e.g., volume, brightness, and keyboard
backlight indicators) and omnipresent after closing either game.
Artifacts remain on screen until log-out or reboot. Artifacts were not
present beforehand.
Artifacts only appeared in Wayland session; not X11/Xorg.
I previously had been running the same games on Ubuntu 22.04 LTS
(GNOME, Wayland) and Kubuntu 22.04 LTS (Plasma, X11/Xorg) on this
computer without issue (kernel 6.2).
* * * * *
Please see subsequent posts for video/images.
Happy to provide any other information as needed. Thanks!
* * * * *
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct 11 01:17:43 2023
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [Radeon Vega Series / Radeon
Vega Mobile Series] [1002:1638] (rev d1) (prog-if 00 [VGA controller])
Subsystem: Lenovo Cezanne [Radeon Vega Series / Radeon Vega Mobile Series]
[17aa:509b]
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-9-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/15/2023
dmi.bios.release: 1.24
dmi.bios.vendor: LENOVO
dmi.bios.version: R1MET54W (1.24 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21A00068US
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76530 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.24
dmi.modalias:
dmi:bvnLENOVO:bvrR1MET54W(1.24):bd05/15/2023:br1.24:efr1.24:svnLENOVO:pn21A00068US:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A00068US:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a:
dmi.product.family: ThinkPad P14s Gen 2a
dmi.product.name: 21A00068US
dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a
dmi.product.version: ThinkPad P14s Gen 2a
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.17-2build1
To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/2038998/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland
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. https://bugs.launchpad.net/bugs/2034619 Title: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland Status in Linux: New Status in Mutter: Fix Released Status in X.Org X server: Fix Released Status in linux package in Ubuntu: Triaged Status in mutter package in Ubuntu: Fix Released Status in linux source package in Mantic: Triaged Status in mutter source package in Mantic: Fix Committed Bug description: [ Impact ] gnome-shell gets unceremoniously SIGKILLed on some Ryzen systems, sometimes when the screen locks, sometimes when launching particular apps. [ Workaround ] Add this to /etc/environment: MUTTER_DEBUG_KMS_THREAD_TYPE=user and then reboot. [ Test Plan ] Not all Ryzen systems (including one I just purchased) are able to reproduce the bug. We have no choice but to leave final verification to the community. Anyone affected should try locking their screen and verify they are not instantly returned to the login screen. [ Where problems could occur ] Anywhere in frame scheduling and particularly for mouse cursor movement since that's what the real-time thread exists to optimize. [ Original Description ] I have this issue on Ubuntu 23.10. Lock screen works only with an external monitor connected. Otherwise the session is ended and the user is logged out and brought to the gdm screen. All works in xorg. ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~beta.1-0ubuntu2 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 22:32:22 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-09-03 (3 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230901.1) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu2 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2034619/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland
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 Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2034619 Title: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland Status in Linux: New Status in Mutter: Fix Released Status in X.Org X server: Fix Released Status in linux package in Ubuntu: Triaged Status in mutter package in Ubuntu: Fix Released Status in linux source package in Mantic: Triaged Status in mutter source package in Mantic: Fix Committed Bug description: [ Impact ] gnome-shell gets unceremoniously SIGKILLed on some Ryzen systems, sometimes when the screen locks, sometimes when launching particular apps. [ Workaround ] Add this to /etc/environment: MUTTER_DEBUG_KMS_THREAD_TYPE=user and then reboot. [ Test Plan ] Not all Ryzen systems (including one I just purchased) are able to reproduce the bug. We have no choice but to leave final verification to the community. Anyone affected should try locking their screen and verify they are not instantly returned to the login screen. [ Where problems could occur ] Anywhere in frame scheduling and particularly for mouse cursor movement since that's what the real-time thread exists to optimize. [ Original Description ] I have this issue on Ubuntu 23.10. Lock screen works only with an external monitor connected. Otherwise the session is ended and the user is logged out and brought to the gdm screen. All works in xorg. ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~beta.1-0ubuntu2 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 22:32:22 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-09-03 (3 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230901.1) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu2 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2034619/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland
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 -- 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/2034619 Title: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland Status in Linux: New Status in Mutter: Fix Released Status in X.Org X server: Fix Released Status in linux package in Ubuntu: Triaged Status in mutter package in Ubuntu: Fix Released Status in linux source package in Mantic: Triaged Status in mutter source package in Mantic: Fix Committed Bug description: [ Impact ] gnome-shell gets unceremoniously SIGKILLed on some Ryzen systems, sometimes when the screen locks, sometimes when launching particular apps. [ Workaround ] Add this to /etc/environment: MUTTER_DEBUG_KMS_THREAD_TYPE=user and then reboot. [ Test Plan ] Not all Ryzen systems (including one I just purchased) are able to reproduce the bug. We have no choice but to leave final verification to the community. Anyone affected should try locking their screen and verify they are not instantly returned to the login screen. [ Where problems could occur ] Anywhere in frame scheduling and particularly for mouse cursor movement since that's what the real-time thread exists to optimize. [ Original Description ] I have this issue on Ubuntu 23.10. Lock screen works only with an external monitor connected. Otherwise the session is ended and the user is logged out and brought to the gdm screen. All works in xorg. ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~beta.1-0ubuntu2 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 22:32:22 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-09-03 (3 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230901.1) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu2 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2034619/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1179524] Re: Bad colors with RDP connection
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: remmina (Ubuntu) Status: Invalid => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to remmina in Ubuntu. https://bugs.launchpad.net/bugs/1179524 Title: Bad colors with RDP connection Status in remmina package in Ubuntu: New Bug description: Ubuntu 13.04 remmina (1.0.0-4ubuntu2) I've used Remmina for quite a while and been fairly pleased with it. After upgrading to 13.04 however the colors coming from my Win7 machine are all messed up. Its as if they were inverted or otherwise skewed. White is white and black is black, but the "Start" button looks weird and sun bursty and most of the colors just seem wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/1179524/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1846461] Re: Disconcerting Folder/Selection flashing when deleting files/folders
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. https://bugs.launchpad.net/bugs/1846461 Title: Disconcerting Folder/Selection flashing when deleting files/folders Status in Nautilus: New Status in nautilus package in Ubuntu: Fix Released Bug description: 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 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Oct 3 11:06:08 2019 InstallationDate: Installed on 2018-05-02 (518 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: nautilus UpgradeStatus: Upgraded to eoan on 2019-09-29 (3 days ago) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1846461/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1893476] [NEW] Broken colors using RDP with Windows 10
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 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Fri Aug 28 21:00:54 2020 ExecutablePath: /usr/bin/remmina InstallationDate: Installed on 2018-05-02 (849 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: remmina UpgradeStatus: Upgraded to focal on 2020-02-24 (185 days ago) ** Affects: remmina (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal wayland-session ** Attachment added: "screenshot of the issue." https://bugs.launchpad.net/bugs/1893476/+attachment/5405529/+files/Screenshot%20from%202020-08-28%2021-04-26.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to remmina in Ubuntu. https://bugs.launchpad.net/bugs/1893476 Title: Broken colors using RDP with Windows 10 Status in remmina package in Ubuntu: New Bug description: 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 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Fri Aug 28 21:00:54 2020 ExecutablePath: /usr/bin/remmina InstallationDate: Installed on 2018-05-02 (849 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: remmina UpgradeStatus: Upgraded to focal on 2020-02-24 (185 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/1893476/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865308] Re: gvfs fails to mount previously working SMB share (from nautilus)
** Also affects: nautilus (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1865308 Title: gvfs fails to mount previously working SMB share (from nautilus) Status in gvfs package in Ubuntu: Confirmed Status in nautilus package in Ubuntu: New Bug description: When accessing my SMB share (samba on linux/openwrt) Nautilus reports that the mount operation failed. I enabled gvfsd debug and got the following debug output. smb: g_vfs_backend_smb_init: default workgroup = 'NULL' smb: Added new job source 0x55be028f8080 (GVfsBackendSmb) smb: Queued new job 0x55be028f9960 (GVfsJobMount) INFO: Current debug levels: all: 10 tdb: 10 printdrivers: 10 lanman: 10 smb: 10 rpc_parse: 10 rpc_srv: 10 rpc_cli: 10 passdb: 10 sam: 10 auth: 10 winbind: 10 vfs: 10 idmap: 10 quota: 10 acls: 10 locking: 10 msdfs: 10 dmapi: 10 registry: 10 scavenger: 10 dns: 10 ldb: 10 tevent: 10 auth_audit: 10 auth_json_audit: 10 kerberos: 10 drs_repl: 10 smb2: 10 smb2_credits: 10 dsdb_audit: 10 dsdb_json_audit: 10 dsdb_password_audit: 10 dsdb_password_json_audit: 10 dsdb_transaction_audit: 10 dsdb_transaction_json_audit: 10 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_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 denied Opening /run/samba/gencache.tdb failed: Permission denied sitename_fetch: No stored sitename for realm '' internal_resolve_name: looking up openwrt#20 (sitename (null)) 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 denied Opening /run/samba/gencache.tdb failed: Permission denied no entry for openwrt#20 found. resolve_lmhosts: Attempting lmhosts lookup for name openwrt<0x20> startlmhosts: Can't open lmhosts file /etc/samba/lmhosts. Error was No such file or directory resolve_wins: WINS server resolution selected and no WINS servers listed. resolve_hosts: Attempting host lookup for name openwrt<0x20> resolve_hosts: getaddrinfo failed for name openwrt [Name or service not known] name_resolve_bcast: Attempting broadcast lookup for name openwrt<0x20> parse_nmb: packet id = 17529 nmb packet from 192.168.42.1(35072) header: id=17529 opcode=Query(0) response=Yes header: flags: bcast=No rec_avail=Yes rec_des=Yes trunc=No auth=Yes header: rcode=0 qdcount=0 ancount=1 nscount=0 arcount=0 answers: nmb_name=OPENWRT<20> rr_type=32 rr_class=1 ttl=259200 answers 0 char *. hex C0A82A01 Got a positive name query response from 192.168.42.1 ( 192.168.42.1 ) remove_duplicate_addrs2: looking for duplicate address/port pairs namecache_store: storing 1 address for openwrt#20: 192.168.42.1 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 denied Opening /run/samba/gencache.tdb failed: Permission denied internal_resolve_name: returning 1 addresses: 192.168.42.1:0 Connecting to 192.168.42.1 at port 445 Socket options: SO_KEEPALIVE = 0 SO_REUSEADDR = 0 SO_BROADCAST = 0 TCP_NODELAY = 1 TCP_KEEPCNT = 9 TCP_KEEPIDLE = 7200 TCP_KEEPINTVL = 75 IPTOS_LOWDELAY = 0 IPTOS_THROUGHPUT = 0 SO_REUSEPORT = 0 SO_SNDBUF = 87040 SO_RCVBUF = 131072 SO_SNDLOWAT = 1 SO_RCVLOWAT = 1 SO_SNDTIMEO = 0 SO_RCVTIMEO = 0 TCP_QUICKACK = 1 TCP_DEFER_ACCEPT = 0 map_errno_from_nt_status: 32 bit codes: code=c20c smb: do_mount - [smb://openwrt/doom; 0] res = -1, cancelled = 0, errno = [103] 'Software caused connection abort' smb: do_mount - (errno != EPERM && errno != EACCES), cancelled = 0, breaking smb: send_reply(0x55be028f9960), failed=1 (Failed to mount Windows share: Software caused connection abort) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1865308/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865308] Re: gvfs fails to mount previously working SMB share (from nautilus)
I wondered why I am still alone, this is a quite essential feature which makes me wonder if there is anything else that I can do to determine the issue in case it cannot be replicated. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1865308 Title: gvfs fails to mount previously working SMB share (from nautilus) Status in gvfs package in Ubuntu: Confirmed Bug description: When accessing my SMB share (samba on linux/openwrt) Nautilus reports that the mount operation failed. I enabled gvfsd debug and got the following debug output. smb: g_vfs_backend_smb_init: default workgroup = 'NULL' smb: Added new job source 0x55be028f8080 (GVfsBackendSmb) smb: Queued new job 0x55be028f9960 (GVfsJobMount) INFO: Current debug levels: all: 10 tdb: 10 printdrivers: 10 lanman: 10 smb: 10 rpc_parse: 10 rpc_srv: 10 rpc_cli: 10 passdb: 10 sam: 10 auth: 10 winbind: 10 vfs: 10 idmap: 10 quota: 10 acls: 10 locking: 10 msdfs: 10 dmapi: 10 registry: 10 scavenger: 10 dns: 10 ldb: 10 tevent: 10 auth_audit: 10 auth_json_audit: 10 kerberos: 10 drs_repl: 10 smb2: 10 smb2_credits: 10 dsdb_audit: 10 dsdb_json_audit: 10 dsdb_password_audit: 10 dsdb_password_json_audit: 10 dsdb_transaction_audit: 10 dsdb_transaction_json_audit: 10 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_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 denied Opening /run/samba/gencache.tdb failed: Permission denied sitename_fetch: No stored sitename for realm '' internal_resolve_name: looking up openwrt#20 (sitename (null)) 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 denied Opening /run/samba/gencache.tdb failed: Permission denied no entry for openwrt#20 found. resolve_lmhosts: Attempting lmhosts lookup for name openwrt<0x20> startlmhosts: Can't open lmhosts file /etc/samba/lmhosts. Error was No such file or directory resolve_wins: WINS server resolution selected and no WINS servers listed. resolve_hosts: Attempting host lookup for name openwrt<0x20> resolve_hosts: getaddrinfo failed for name openwrt [Name or service not known] name_resolve_bcast: Attempting broadcast lookup for name openwrt<0x20> parse_nmb: packet id = 17529 nmb packet from 192.168.42.1(35072) header: id=17529 opcode=Query(0) response=Yes header: flags: bcast=No rec_avail=Yes rec_des=Yes trunc=No auth=Yes header: rcode=0 qdcount=0 ancount=1 nscount=0 arcount=0 answers: nmb_name=OPENWRT<20> rr_type=32 rr_class=1 ttl=259200 answers 0 char *. hex C0A82A01 Got a positive name query response from 192.168.42.1 ( 192.168.42.1 ) remove_duplicate_addrs2: looking for duplicate address/port pairs namecache_store: storing 1 address for openwrt#20: 192.168.42.1 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 denied Opening /run/samba/gencache.tdb failed: Permission denied internal_resolve_name: returning 1 addresses: 192.168.42.1:0 Connecting to 192.168.42.1 at port 445 Socket options: SO_KEEPALIVE = 0 SO_REUSEADDR = 0 SO_BROADCAST = 0 TCP_NODELAY = 1 TCP_KEEPCNT = 9 TCP_KEEPIDLE = 7200 TCP_KEEPINTVL = 75 IPTOS_LOWDELAY = 0 IPTOS_THROUGHPUT = 0 SO_REUSEPORT = 0 SO_SNDBUF = 87040 SO_RCVBUF = 131072 SO_SNDLOWAT = 1 SO_RCVLOWAT = 1 SO_SNDTIMEO = 0 SO_RCVTIMEO = 0 TCP_QUICKACK = 1 TCP_DEFER_ACCEPT = 0 map_errno_from_nt_status: 32 bit codes: code=c20c smb: do_mount - [smb://openwrt/doom; 0] res = -1, cancelled = 0, errno = [103] 'Software caused connection abort' smb: do_mount - (errno != EPERM && errno != EACCES), cancelled = 0, breaking smb: send_reply(0x55be028f9960), failed=1 (Failed to mount Windows share: Software caused connection abort) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1865308/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launch
[Desktop-packages] [Bug 1865308] [NEW] gvfs fails to mount previously working SMB share (from nautilus)
Public bug reported: When accessing my SMB share (samba on linux/openwrt) Nautilus reports that the mount operation failed. I enabled gvfsd debug and got the following debug output. smb: g_vfs_backend_smb_init: default workgroup = 'NULL' smb: Added new job source 0x55be028f8080 (GVfsBackendSmb) smb: Queued new job 0x55be028f9960 (GVfsJobMount) INFO: Current debug levels: all: 10 tdb: 10 printdrivers: 10 lanman: 10 smb: 10 rpc_parse: 10 rpc_srv: 10 rpc_cli: 10 passdb: 10 sam: 10 auth: 10 winbind: 10 vfs: 10 idmap: 10 quota: 10 acls: 10 locking: 10 msdfs: 10 dmapi: 10 registry: 10 scavenger: 10 dns: 10 ldb: 10 tevent: 10 auth_audit: 10 auth_json_audit: 10 kerberos: 10 drs_repl: 10 smb2: 10 smb2_credits: 10 dsdb_audit: 10 dsdb_json_audit: 10 dsdb_password_audit: 10 dsdb_password_json_audit: 10 dsdb_transaction_audit: 10 dsdb_transaction_json_audit: 10 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_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 denied Opening /run/samba/gencache.tdb failed: Permission denied sitename_fetch: No stored sitename for realm '' internal_resolve_name: looking up openwrt#20 (sitename (null)) 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 denied Opening /run/samba/gencache.tdb failed: Permission denied no entry for openwrt#20 found. resolve_lmhosts: Attempting lmhosts lookup for name openwrt<0x20> startlmhosts: Can't open lmhosts file /etc/samba/lmhosts. Error was No such file or directory resolve_wins: WINS server resolution selected and no WINS servers listed. resolve_hosts: Attempting host lookup for name openwrt<0x20> resolve_hosts: getaddrinfo failed for name openwrt [Name or service not known] name_resolve_bcast: Attempting broadcast lookup for name openwrt<0x20> parse_nmb: packet id = 17529 nmb packet from 192.168.42.1(35072) header: id=17529 opcode=Query(0) response=Yes header: flags: bcast=No rec_avail=Yes rec_des=Yes trunc=No auth=Yes header: rcode=0 qdcount=0 ancount=1 nscount=0 arcount=0 answers: nmb_name=OPENWRT<20> rr_type=32 rr_class=1 ttl=259200 answers 0 char *. hex C0A82A01 Got a positive name query response from 192.168.42.1 ( 192.168.42.1 ) remove_duplicate_addrs2: looking for duplicate address/port pairs namecache_store: storing 1 address for openwrt#20: 192.168.42.1 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 denied Opening /run/samba/gencache.tdb failed: Permission denied internal_resolve_name: returning 1 addresses: 192.168.42.1:0 Connecting to 192.168.42.1 at port 445 Socket options: SO_KEEPALIVE = 0 SO_REUSEADDR = 0 SO_BROADCAST = 0 TCP_NODELAY = 1 TCP_KEEPCNT = 9 TCP_KEEPIDLE = 7200 TCP_KEEPINTVL = 75 IPTOS_LOWDELAY = 0 IPTOS_THROUGHPUT = 0 SO_REUSEPORT = 0 SO_SNDBUF = 87040 SO_RCVBUF = 131072 SO_SNDLOWAT = 1 SO_RCVLOWAT = 1 SO_SNDTIMEO = 0 SO_RCVTIMEO = 0 TCP_QUICKACK = 1 TCP_DEFER_ACCEPT = 0 map_errno_from_nt_status: 32 bit codes: code=c20c smb: do_mount - [smb://openwrt/doom; 0] res = -1, cancelled = 0, errno = [103] 'Software caused connection abort' smb: do_mount - (errno != EPERM && errno != EACCES), cancelled = 0, breaking smb: send_reply(0x55be028f9960), failed=1 (Failed to mount Windows share: Software caused connection abort) ** Affects: gvfs (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1865308 Title: gvfs fails to mount previously working SMB share (from nautilus) Status in gvfs package in Ubuntu: New Bug description: When accessing my SMB share (samba on linux/openwrt) Nautilus reports that the mount operation failed. I enabled gvfsd debug and got the following debug output. smb: g_vfs_backend_smb_init: default workgroup = 'NULL' smb: Added new job source 0x55be028f8080 (GVfsBackendSmb) smb: Queued new job 0x55be028f9960 (GVfsJobMount) INFO: Current debug levels: all: 10 tdb: 10 printdrivers: 10 lanman: 10 smb: 10 rpc_parse: 10 rpc_srv: 10 rpc_cli: 10 passdb: 10 sam: 10 auth: 10
[Desktop-packages] [Bug 1846461] Re: Disconcerting Folder/Selection flashing when deleting files/folders
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 of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1846461 Title: Disconcerting Folder/Selection flashing when deleting files/folders Status in nautilus package in Ubuntu: New Bug description: 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 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Oct 3 11:06:08 2019 InstallationDate: Installed on 2018-05-02 (518 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: nautilus UpgradeStatus: Upgraded to eoan on 2019-09-29 (3 days ago) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1846461/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1846461] Re: Disconcerting Folder/Selection flashing when deleting files/folders
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" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1846461/+attachment/5293925/+files/Screencast%20from%2003.10.2019%2011%3A29%3A21.webm -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1846461 Title: Disconcerting Folder/Selection flashing when deleting files/folders Status in nautilus package in Ubuntu: New Bug description: 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 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Oct 3 11:06:08 2019 InstallationDate: Installed on 2018-05-02 (518 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: nautilus UpgradeStatus: Upgraded to eoan on 2019-09-29 (3 days ago) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1846461/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1846461] [NEW] Disconcerting Folder/Selection flashing when deleting files/folders
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 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Oct 3 11:06:08 2019 InstallationDate: Installed on 2018-05-02 (518 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: nautilus UpgradeStatus: Upgraded to eoan on 2019-09-29 (3 days ago) usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan third-party-packages wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1846461 Title: Disconcerting Folder/Selection flashing when deleting files/folders Status in nautilus package in Ubuntu: New Bug description: 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 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Oct 3 11:06:08 2019 InstallationDate: Installed on 2018-05-02 (518 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: nautilus UpgradeStatus: Upgraded to eoan on 2019-09-29 (3 days ago) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1846461/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1724919] Re: Bluetooth headphones only use A2DP when connected manually
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 the Sony WH-1000XM2. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1724919 Title: Bluetooth headphones only use A2DP when connected manually Status in alsa-driver package in Ubuntu: Won't Fix Bug description: Issue with Sony MDR-1ABT Bluetooth headphones: Once paired, the headphones will be connected automatically whenever they are switched on. However when connected this way, only the HSP/HFP profile will work and trying to change to A2DP in sound settings does nothing. If the headphones are then manually disconnected and reconnected from Bluetooth settings, they will initially use HSP/HFP but then selecting A2DP in sound settings will successfully make them use A2DP. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: neil 1443 F pulseaudio /dev/snd/pcmC0D0c: neil 1443 F...m pulseaudio /dev/snd/controlC0: neil 1443 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Oct 19 19:12:59 2017 InstallationDate: Installed on 2017-10-19 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: MDR-1ABT Symptom_Type: None of the above Title: [MDR-1ABT, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: Default string dmi.board.name: Z270N-WIFI-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd07/06/2017:svnGigabyteTechnologyCo.,Ltd.:pnZ270N-WIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ270N-WIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Z270N-WIFI dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1724919/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1733002] Re: Google Online Account Two Factor with hardware key fails immediately
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 gnome-online-accounts: Unknown Status in gnome-online-accounts package in Ubuntu: Triaged Bug description: The hardware key authentication two factor fails immediately with a web based retry dialogue when connecting a Google account to the online accounts in settings using a hardware key second factor. Steps to reproduce: 1. Set Google Account to default to a hardware security key like a Yubikey or other FIDO standard key after having two factor authentication enabled on your Google Account. 2. Open Online accounts 3. Add a Google Account 4. Enter google email address 5. Enter google password 6. (this is the login flow of two factor, if default is the hardware key the error should appear). Work around: Choose use another method to authenticate: enter the authentication code and you will proceed. Expectations were: The ability to use the hardware key to authenticate as the second factor. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.26.1-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4 Uname: Linux 4.13.0-16-lowlatency x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Nov 17 16:01:11 2017 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gnome-control-center ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash PATH=(custom, user) LANG=en_US.UTF-8 SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-online-accounts/+bug/1733002/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1822392] Re: gsd-media-keys fails to adjust the screen brightness after unlocking
meout 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]: doommaster: Executing command [USER=root] [TTY=unknown] [CWD=/home/doommaster] [COMMAND=/usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 93] Mär 30 01:17:55 pkexec[851]: pam_unix(polkit-1:session): session opened for user root by (uid=1000) Mär 30 01:17:55 pkexec[851]: doommaster: Executing command [USER=root] [TTY=unknown] [CWD=/home/doommaster] [COMMAND=/usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 139] Mär 30 01:17:55 pkexec[857]: pam_unix(polkit-1:session): session opened for user root by (uid=1000) Mär 30 01:17:55 pkexec[857]: doommaster: Executing command [USER=root] [TTY=unknown] [CWD=/home/doommaster] [COMMAND=/usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 185] Mär 30 01:17:55 pkexec[863]: pam_unix(polkit-1:session): session opened for user root by (uid=1000) Mär 30 01:17:55 pkexec[863]: doommaster: Executing command [USER=root] [TTY=unknown] [CWD=/home/doommaster] [COMMAND=/usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 231] Mär 30 01:17:55 pkexec[869]: pam_unix(polkit-1:session): session opened for user root by (uid=1000) Mär 30 01:17:55 pkexec[869]: doommaster: Executing command [USER=root] [TTY=unknown] [CWD=/home/doommaster] [COMMAND=/usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 277] Mär 30 01:18:03 org.gnome.Shell.desktop[14229]: Window manager warning: last_user_time (99401388) is greater than comparison timestamp (99401386). This most likely represents a buggy client sending inaccurate t Mär 30 01:18:03 org.gnome.Shell.desktop[14229]: Window manager warning: W181 (fish /ho) appears to be one of the offending windows with a timestamp of 99401388. Working around... ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-settings-daemon 3.30.1.2-1ubuntu3.1 ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20 Uname: Linux 4.18.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Mar 30 01:22:26 2019 ExecutablePath: /usr/lib/gnome-settings-daemon/gsd-media-keys InstallationDate: Installed on 2018-05-02 (331 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to cosmic on 2018-12-24 (95 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1822392/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1427877] Re: Media, brightness and volume keys don't work with GNOME 3.15.90
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 Status in GNOME Settings Daemon: Unknown Status in GNOME Shell: Invalid Status in Ubuntu GNOME: Fix Released Status in gnome-settings-daemon package in Ubuntu: Fix Released Bug description: After upgrading Ubuntu 15.04 Vivid to use GNOME 3.15.90 (by using gnome3-team/gnome3, gnome3-team/gnome3-staging ppas) media, brightness and volume keys from my laptop keyboard stop to work after working some time in a session or after suspending the computer. If I restart my computer media keys work again. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: gnome-settings-daemon 3.15.90-0ubuntu1~vivid1 [origin: LP-PPA-gnome3-team-gnome3-staging] ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Mar 3 23:07:33 2015 InstallationDate: Installed on 2014-10-22 (132 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 (20140923) SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1427877/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1822392] Re: gsd-media-keys fails to adjust the screen brightness after unlocking
on 19.04 the issue still exists. gsd-media-keys seems to be the problem after all... -- 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/1822392 Title: gsd-media-keys fails to adjust the screen brightness after unlocking Status in gnome-settings-daemon package in Ubuntu: New Bug description: Whne my machine sat for some time (laptop, screen off) it is not possible to change the screen brighness of the display for some time after unlocking. After 3-5 minutes it will eventually just work again. journalctl logs the following är 30 01:17:02 dbus-daemon[975]: [system] Activating via systemd: service name='net.reactivated.Fprint' unit='fprintd.service' requested by ':1.212' (uid=1000 pid=14229 comm="/usr/bin/gnome-shell " label="uncon Mär 30 01:17:02 systemd[1]: Starting Fingerprint Authentication Daemon... Mär 30 01:17:02 dbus-daemon[975]: [system] Successfully activated service 'net.reactivated.Fprint' Mär 30 01:17:02 systemd[1]: Started Fingerprint Authentication Daemon. Mär 30 01:17:06 gdm-password][605]: gkr-pam: unlocked login keyring Mär 30 01:17:45 dbus-daemon[14209]: [session uid=1000 pid=14209] Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service' requested by ':1.137' (uid=1000 pid=808 comm="/usr/ Mär 30 01:17:45 systemd[14145]: Starting GNOME Terminal Server... Mär 30 01:17:45 gnome-terminal-server[813]: Display does not support owner-change; copy/paste will be broken! Mär 30 01:17:45 dbus-daemon[14209]: [session uid=1000 pid=14209] Successfully activated service 'org.gnome.Terminal' Mär 30 01:17:45 systemd[14145]: Started GNOME Terminal Server. Mär 30 01:17:45 org.gnome.SettingsDaemon.MediaKeys.desktop[14428]: # watch_fast: "/org/gnome/desktop/interface/" (establishing: 0, active: 0) Mär 30 01:17:45 org.gnome.SettingsDaemon.MediaKeys.desktop[14428]: # watch_fast: "/org/gnome/settings-daemon/peripherals/mouse/" (establishing: 0, active: 0) Mär 30 01:17:45 org.gnome.SettingsDaemon.MediaKeys.desktop[14428]: # watch_fast: "/org/gnome/desktop/sound/" (establishing: 0, active: 0) Mär 30 01:17:45 org.gnome.SettingsDaemon.MediaKeys.desktop[14428]: # watch_fast: "/org/gnome/desktop/privacy/" (establishing: 0, active: 0) Mär 30 01:17:45 org.gnome.SettingsDaemon.MediaKeys.desktop[14428]: # watch_fast: "/org/gnome/desktop/wm/preferences/" (establishing: 0, active: 0) Mär 30 01:17:45 org.gnome.SettingsDaemon.MediaKeys.desktop[14428]: # watch_fast: "/org/gnome/settings-daemon/plugins/xsettings/" (establishing: 0, active: 0) Mär 30 01:17:45 org.gnome.SettingsDaemon.MediaKeys.desktop[14428]: # watch_fast: "/org/gnome/desktop/a11y/" (establishing: 0, active: 0) Mär 30 01:17:45 org.gnome.SettingsDaemon.MediaKeys.desktop[14428]: # watch_established: "/org/gnome/desktop/interface/" (establishing: 1) Mär 30 01:17:45 org.gnome.SettingsDaemon.MediaKeys.desktop[14428]: # watch_established: "/org/gnome/settings-daemon/peripherals/mouse/" (establishing: 1) Mär 30 01:17:45 org.gnome.SettingsDaemon.MediaKeys.desktop[14428]: # watch_established: "/org/gnome/desktop/sound/" (establishing: 1) Mär 30 01:17:45 org.gnome.SettingsDaemon.MediaKeys.desktop[14428]: # watch_established: "/org/gnome/desktop/privacy/" (establishing: 1) Mär 30 01:17:45 org.gnome.SettingsDaemon.MediaKeys.desktop[14428]: # watch_established: "/org/gnome/desktop/wm/preferences/" (establishing: 1) Mär 30 01:17:45 org.gnome.SettingsDaemon.MediaKeys.desktop[14428]: # watch_established: "/org/gnome/settings-daemon/plugins/xsettings/" (establishing: 1) Mär 30 01:17:45 org.gnome.SettingsDaemon.MediaKeys.desktop[14428]: # watch_established: "/org/gnome/desktop/a11y/" (establishing: 1) Mär 30 01:17:45 org.gnome.SettingsDaemon.MediaKeys.desktop[14428]: # watch_fast: "/org/gnome/terminal/legacy/" (establishing: 0, active: 0) Mär 30 01:17:45 org.gnome.SettingsDaemon.MediaKeys.desktop[14428]: # unwatch_fast: "/org/gnome/terminal/legacy/" (active: 0, establishing: 1) Mär 30 01:17:45 org.gnome.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: 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]: doommaster: Executing command [USER=root] [TTY=unknown] [CWD=/home/doommaster] [COMMAND=/usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 93] Mär 30 01:17:55 pkexec[851]: pam_unix(po
[Desktop-packages] [Bug 1822392] [NEW] gsd-media-keys fails to adjust the screen brightness after unlocking
Public bug reported: Whne my machine sat for some time (laptop, screen off) it is not possible to change the screen brighness of the display for some time after unlocking. After 3-5 minutes it will eventually just work again. journalctl logs the following är 30 01:17:02 dbus-daemon[975]: [system] Activating via systemd: service name='net.reactivated.Fprint' unit='fprintd.service' requested by ':1.212' (uid=1000 pid=14229 comm="/usr/bin/gnome-shell " label="uncon Mär 30 01:17:02 systemd[1]: Starting Fingerprint Authentication Daemon... Mär 30 01:17:02 dbus-daemon[975]: [system] Successfully activated service 'net.reactivated.Fprint' Mär 30 01:17:02 systemd[1]: Started Fingerprint Authentication Daemon. Mär 30 01:17:06 gdm-password][605]: gkr-pam: unlocked login keyring Mär 30 01:17:45 dbus-daemon[14209]: [session uid=1000 pid=14209] Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service' requested by ':1.137' (uid=1000 pid=808 comm="/usr/ Mär 30 01:17:45 systemd[14145]: Starting GNOME Terminal Server... Mär 30 01:17:45 gnome-terminal-server[813]: Display does not support owner-change; copy/paste will be broken! Mär 30 01:17:45 dbus-daemon[14209]: [session uid=1000 pid=14209] Successfully activated service 'org.gnome.Terminal' Mär 30 01:17:45 systemd[14145]: Started GNOME Terminal Server. Mär 30 01:17:45 org.gnome.SettingsDaemon.MediaKeys.desktop[14428]: # watch_fast: "/org/gnome/desktop/interface/" (establishing: 0, active: 0) Mär 30 01:17:45 org.gnome.SettingsDaemon.MediaKeys.desktop[14428]: # watch_fast: "/org/gnome/settings-daemon/peripherals/mouse/" (establishing: 0, active: 0) Mär 30 01:17:45 org.gnome.SettingsDaemon.MediaKeys.desktop[14428]: # watch_fast: "/org/gnome/desktop/sound/" (establishing: 0, active: 0) Mär 30 01:17:45 org.gnome.SettingsDaemon.MediaKeys.desktop[14428]: # watch_fast: "/org/gnome/desktop/privacy/" (establishing: 0, active: 0) Mär 30 01:17:45 org.gnome.SettingsDaemon.MediaKeys.desktop[14428]: # watch_fast: "/org/gnome/desktop/wm/preferences/" (establishing: 0, active: 0) Mär 30 01:17:45 org.gnome.SettingsDaemon.MediaKeys.desktop[14428]: # watch_fast: "/org/gnome/settings-daemon/plugins/xsettings/" (establishing: 0, active: 0) Mär 30 01:17:45 org.gnome.SettingsDaemon.MediaKeys.desktop[14428]: # watch_fast: "/org/gnome/desktop/a11y/" (establishing: 0, active: 0) Mär 30 01:17:45 org.gnome.SettingsDaemon.MediaKeys.desktop[14428]: # watch_established: "/org/gnome/desktop/interface/" (establishing: 1) Mär 30 01:17:45 org.gnome.SettingsDaemon.MediaKeys.desktop[14428]: # watch_established: "/org/gnome/settings-daemon/peripherals/mouse/" (establishing: 1) Mär 30 01:17:45 org.gnome.SettingsDaemon.MediaKeys.desktop[14428]: # watch_established: "/org/gnome/desktop/sound/" (establishing: 1) Mär 30 01:17:45 org.gnome.SettingsDaemon.MediaKeys.desktop[14428]: # watch_established: "/org/gnome/desktop/privacy/" (establishing: 1) Mär 30 01:17:45 org.gnome.SettingsDaemon.MediaKeys.desktop[14428]: # watch_established: "/org/gnome/desktop/wm/preferences/" (establishing: 1) Mär 30 01:17:45 org.gnome.SettingsDaemon.MediaKeys.desktop[14428]: # watch_established: "/org/gnome/settings-daemon/plugins/xsettings/" (establishing: 1) Mär 30 01:17:45 org.gnome.SettingsDaemon.MediaKeys.desktop[14428]: # watch_established: "/org/gnome/desktop/a11y/" (establishing: 1) Mär 30 01:17:45 org.gnome.SettingsDaemon.MediaKeys.desktop[14428]: # watch_fast: "/org/gnome/terminal/legacy/" (establishing: 0, active: 0) Mär 30 01:17:45 org.gnome.SettingsDaemon.MediaKeys.desktop[14428]: # unwatch_fast: "/org/gnome/terminal/legacy/" (active: 0, establishing: 1) Mär 30 01:17:45 org.gnome.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: 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]: doommaster: Executing command [USER=root] [TTY=unknown] [CWD=/home/doommaster] [COMMAND=/usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 93] Mär 30 01:17:55 pkexec[851]: pam_unix(polkit-1:session): session opened for user root by (uid=1000) Mär 30 01:17:55 pkexec[851]: doommaster: Executing command [USER=root] [TTY=unknown] [CWD=/home/doommaster] [COMMAND=/usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 139] Mär 30 01:17:55 pkexec[857]: pam_unix(polkit-1:session): session opened for user root by (uid=1000) Mär 30 01:17:55 pkexec[857]: doommaster: Executing command [USER=root] [TTY=unknown] [CWD=/home/doommaster] [COM
[Desktop-packages] [Bug 1363003] [NEW] Nautilus segfailts in certtain folder on libgdk_pixbuf-2.0.so.0.3000.7
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): GdkPixbuf-CRITICAL **: gdk_pixbuf_composite: assertion 'dest_y = 0 dest_y + dest_height = dest-height' failed Segmentation fault (core dumped) Version: GNOME nautilus 3.10.1 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1363003 Title: Nautilus segfailts in certtain folder on libgdk_pixbuf-2.0.so.0.3000.7 Status in “nautilus” package in Ubuntu: New Bug description: 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): GdkPixbuf-CRITICAL **: gdk_pixbuf_composite: assertion 'dest_y = 0 dest_y + dest_height = dest-height' failed Segmentation fault (core dumped) Version: GNOME nautilus 3.10.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1363003/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1363003] Re: Nautilus segfailts in certtain folder on libgdk_pixbuf-2.0.so.0.3000.7
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 nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1363003 Title: Nautilus segfailts in certtain folder on libgdk_pixbuf-2.0.so.0.3000.7 Status in “nautilus” package in Ubuntu: New Bug description: 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): GdkPixbuf-CRITICAL **: gdk_pixbuf_composite: assertion 'dest_y = 0 dest_y + dest_height = dest-height' failed Segmentation fault (core dumped) Version: GNOME nautilus 3.10.1 --- ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 14.04 GsettingsChanges: org.gnome.nautilus.list-view default-column-order ['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where'] InstallationDate: Installed on 2014-08-20 (8 days ago) InstallationMedia: Ubuntu-GNOME 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) Package: nautilus 1:3.10.1-0ubuntu9.3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Tags: trusty Uname: Linux 3.13.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1363003/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1363003] usr_lib_nautilus.txt
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 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 nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1363003 Title: Nautilus segfailts in certtain folder on libgdk_pixbuf-2.0.so.0.3000.7 Status in “nautilus” package in Ubuntu: New Bug description: 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): GdkPixbuf-CRITICAL **: gdk_pixbuf_composite: assertion 'dest_y = 0 dest_y + dest_height = dest-height' failed Segmentation fault (core dumped) Version: GNOME nautilus 3.10.1 --- ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 14.04 GsettingsChanges: org.gnome.nautilus.list-view default-column-order ['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where'] InstallationDate: Installed on 2014-08-20 (8 days ago) InstallationMedia: Ubuntu-GNOME 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) Package: nautilus 1:3.10.1-0ubuntu9.3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Tags: trusty Uname: Linux 3.13.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1363003/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1363003] ProcEnviron.txt
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. https://bugs.launchpad.net/bugs/1363003 Title: Nautilus segfailts in certtain folder on libgdk_pixbuf-2.0.so.0.3000.7 Status in “nautilus” package in Ubuntu: New Bug description: 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): GdkPixbuf-CRITICAL **: gdk_pixbuf_composite: assertion 'dest_y = 0 dest_y + dest_height = dest-height' failed Segmentation fault (core dumped) Version: GNOME nautilus 3.10.1 --- ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 14.04 GsettingsChanges: org.gnome.nautilus.list-view default-column-order ['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where'] InstallationDate: Installed on 2014-08-20 (8 days ago) InstallationMedia: Ubuntu-GNOME 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) Package: nautilus 1:3.10.1-0ubuntu9.3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Tags: trusty Uname: Linux 3.13.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1363003/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1363003] Re: Nautilus segfailts in certtain folder on libgdk_pixbuf-2.0.so.0.3000.7
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 libgdk_pixbuf-2.0.so.0.3000.7[7fac52b46000+1f000] (nautilus:25779): GdkPixbuf-CRITICAL **: gdk_pixbuf_composite: assertion 'dest_y = 0 dest_y + dest_height = dest-height' failed Segmentation fault (core dumped) Version: GNOME nautilus 3.10.1 + --- + ApportVersion: 2.14.1-0ubuntu3.3 + Architecture: amd64 + CurrentDesktop: GNOME + DistroRelease: Ubuntu 14.04 + GsettingsChanges: org.gnome.nautilus.list-view default-column-order ['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where'] + InstallationDate: Installed on 2014-08-20 (8 days ago) + InstallationMedia: Ubuntu-GNOME 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) + Package: nautilus 1:3.10.1-0ubuntu9.3 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 + Tags: trusty + Uname: Linux 3.13.0-34-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: Dependencies.txt https://bugs.launchpad.net/bugs/1363003/+attachment/4189936/+files/Dependencies.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1363003 Title: Nautilus segfailts in certtain folder on libgdk_pixbuf-2.0.so.0.3000.7 Status in “nautilus” package in Ubuntu: New Bug description: 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): GdkPixbuf-CRITICAL **: gdk_pixbuf_composite: assertion 'dest_y = 0 dest_y + dest_height = dest-height' failed Segmentation fault (core dumped) Version: GNOME nautilus 3.10.1 --- ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 14.04 GsettingsChanges: org.gnome.nautilus.list-view default-column-order ['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where'] InstallationDate: Installed on 2014-08-20 (8 days ago) InstallationMedia: Ubuntu-GNOME 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) Package: nautilus 1:3.10.1-0ubuntu9.3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Tags: trusty Uname: Linux 3.13.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1363003/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1041790] Re: [snb] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001, workaround i915.semaphores=0
** 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. https://bugs.launchpad.net/bugs/1041790 Title: [snb] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001, workaround i915.semaphores=0 Status in X.org xf86-video-intel: In Progress Status in “linux” package in Ubuntu: Incomplete Status in “sandybridge-meta” package in Ubuntu: Confirmed Status in “xserver-xorg-video-intel” package in Ubuntu: Triaged Bug description: X locks up periodically for a 2 to ten seconds at a time and this crash log gets generated. It's significantly more than several times a day but not quite continuous. If you indeed have this bug, that should stop the lockups from happening. Irrespective, please file a new bug report so your hardware may be tracked. WORKAROUND: Edit your /etc/default/grub from: GRUB_CMDLINE_LINUX_DEFAULT=quiet splash to: GRUB_CMDLINE_LINUX_DEFAULT=quiet splash i915.semaphores=0 run the following and reboot: sudo update-grub The side effects of this is rendering throughput is dropped by 10% with SNA, or as much as 3x with UXA. OpenGL performance is likely to be reduced by about 30%. More CPU time is spent waiting for the GPU with rc6 disabled, so increased power consumption. ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: xserver-xorg-video-intel 2:2.20.3-0ubuntu1 Uname: Linux 3.6.0-rc3-git-20120826.1015 x86_64 ApportVersion: 2.5.1-0ubuntu2 Architecture: amd64 Chipset: sandybridge-m-gt2 Date: Sun Aug 26 16:06:32 2012 DistroCodename: quantal DistroVariant: ubuntu DuplicateSignature: [sandybridge-m-gt2] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001 Ubuntu 12.10 EcryptfsInUse: Yes ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py GpuHangFrequency: Continuously InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120724.2) InterpreterPath: /usr/bin/python3.2mu MachineType: Dell Inc. Dell System XPS L502X ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gpu-error-intel.py ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.6.0-rc3-git-20120826.1015 root=UUID=135c8090-427c-460a-909d-eff262cd44b6 ro quiet splash vt.handoff=7 RelatedPackageVersions: xserver-xorg 1:7.7+1ubuntu3 libdrm2 2.4.38-0ubuntu2 xserver-xorg-video-intel 2:2.20.3-0ubuntu1 SourcePackage: xserver-xorg-video-intel Title: [sandybridge-m-gt2] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001 UdevDb: Error: [Errno 2] No such file or directory: 'udevadm' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 05/29/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0NJT03 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA11:bd05/29/2012:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0NJT03:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L502X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1041790/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 182473] Re: rtl8187 drops connection
*** 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. https://bugs.launchpad.net/bugs/182473 Title: rtl8187 drops connection Status in The Linux Kernel: Invalid Status in “linux” package in Ubuntu: In Progress Status in “lynx” package in Ubuntu: Invalid Bug description: I have a ASUS P5K motherboard with integrated wireless based on rtl8187. In Hardy (haven't tried other Ubuntu versions) the connection often suddenly fails, with the software not noticing anything. Nothing is logged in dmesg or syslog except for (sometimes): WEP decrypt failed (ICV) I have noticed this string also appears in the log at times when the interface does _not_ fail. The computer continues on oblivious to the fact that it has just lost its network connection (networkmanager is not installed, but gnome's network monitor applet indicates a good connection). In fact, a wireshark dump indicates that the computer still thinks it is sending 802.11 frames, but monitoring from another computer (with a reliable wireless driver) indicates that nothing is being sent from the affected computer, even while the AP is chugging along trying to contact a host which has mysteriously dropped offline. I have noticed this problem across kernel images (2.6.24-3-generic and 2.6.24-4-generic to be specific). In one instance, I found that modprobing the module out and back in again fixed it, while another time this caused modprobe to use 100% CPU and become unresponsive, even to kill signals (Yeah, the kill -9 kind). If any more information is necessary please ask and I'll do my best. This also effects Intrepid Ibex/2.6.27-7-generic To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/182473/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
