[Desktop-packages] [Bug 1827790] Re: Dell XPS 13 9380 - Screen flashes
*** This bug is a duplicate of bug 1826125 *** https://bugs.launchpad.net/bugs/1826125 I have some doubt that this is a duplicate of bug 1826125, though I see how they are similar. I'm experiencing the same issue described in this bug, and the visual effect is quite different than the photos and videos attached to the other bug. In the other one, the issue appears to involve different parts of the display flickering around, or different parts of the screen getting "out of sync" so it looks like there are horizontal bands. The problem in the other bug is also described as quite frequent/constant. I'm not experiencing any of that, but I am experiencing what Daniel C describes in this bug: my entire screen flashes quite brightly for a split second, then calms back down. The effect is uniform across the screen, there's no banding or shifting that I can see. It only happens once every few minutes, not constantly as described in the other bug. The flashing is most noticeable when the "Night Light" effect is active in the evening, though I believe I've also seen it happen during the day. One other important distinction: like Daniel C, I have an XPS 9380 with the non-touch 1080p display, and I wiped Dell's pre-installed 18.04 and installed 19.04 instead. The other bug has several references in the comments to it affecting the XPS 9380 with the "4k" display. So I believe the flashing described in this bug is a different problem with a different panel. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1827790 Title: Dell XPS 13 9380 - Screen flashes Status in xorg package in Ubuntu: Confirmed Bug description: Hello, I have a new 2019 Dell XPS 13 (9380). I ordered the official Ubuntu edition from Dell which came with 18.04, but I've since wiped it and installed 19.04 from a fresh ISO download. This is the non-touch non- 4K version (13-inch 1080p). Every so often (maybe a couple of times per minute), the screen flashes brighter, as if the brightness has been turned up momentarily and then back down again. I previously had an issue with the brightness / colours changing slightly when I opened menus or if the screen content changed slightly, but I fixed that by disabling Dynamic Brightness in the BIOS. It is definitely a better experience with that turned off. However the screen flashing still persists. I booted a live image of Fedora 30 now that it has been released, and so far I have not seen the screen flashing, so I do not think the hardware is faulty. I ran apport-bug, so hopefully the collected information has been attached. Thank you. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 5 15:59:45 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af] InstallationDate: Installed on 2019-04-28 (6 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. XPS 13 9380 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=fcb75d61-4e46-4391-8800-ccef7ff04f70 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 0KTW76 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd03/29/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.product.sku: 08AF dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1827790/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 1825449] Re: Object Gio.Settings (...), has been already deallocated — impossible to access it. (from messageTray.js:195)
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1825449 Title: Object Gio.Settings (...), has been already deallocated — impossible to access it. (from messageTray.js:195) Status in gnome-shell package in Ubuntu: Expired Bug description: gnome-shell[1779]: Object Gio.Settings (0x5563611f1ba0), has been already deallocated — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. == Stack trace for context 0x55635b5da210 == org.gnome.Shell.desktop[1779]: #0 55635d2d6848 i resource:///org/gnome/shell/ui/messageTray.js:195 (7f76fa393e50 @ 22) [...] ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0+git20190410-1ubuntu1 Uname: Linux 5.1.0-050100rc5-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 18 21:00:01 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-12-02 (137 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2018-12-02 (137 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1825449/+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 1825559] Re: Upgrading 18.10 to 19.04: cannot leave overview mode, computer needs to be restarted
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1825559 Title: Upgrading 18.10 to 19.04: cannot leave overview mode, computer needs to be restarted Status in gnome-shell package in Ubuntu: Expired Bug description: I've upgraded my Ubuntu 18.10 to 19.04. Everything looked okey, however if I enter gnome shell "overview mode" I cannot leave it anymore, I can't select any window, type to search etc, and all my windows are in the foreground, covering the search bar etc, but not possible to select them. Simply I can't do anything. I can launch applications from the dock but cannot see and access them anymore. So basically I stuck in overview mode which does not work too much. What I can do, is to use the top panel to log out. If I do that, and login again, I only get a black screen and nothing more. I have to press the power button at that point to shut the computer off, so I can turn on again. It seems everything works, just entering into that "overview mode" kills everything then and only reboot helps from that point. Sorry, I am not sure what the official name of the gnome3 shell "overview mode" possibly I used the wrong terminology. Also, my bad English cannot help either to express the problem well enough, I guess. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1825559/+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 1825739] Re: [X555LJ, Realtek ALC3236, Black Headphone Out, Right] Sound is distorted
[Expired for alsa-driver (Ubuntu) because there has been no activity for 60 days.] ** Changed in: alsa-driver (Ubuntu) Status: Incomplete => Expired -- 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/1825739 Title: [X555LJ, Realtek ALC3236, Black Headphone Out, Right] Sound is distorted Status in alsa-driver package in Ubuntu: Expired Status in linux package in Ubuntu: Expired Bug description: I can hear songs okay with my speaker in laptop, but when i connect headphone in to 3.5mm jack in laptop I hear songs with crackling sound. I'm dual booting with windows. My headphones works fine in windows 10 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: devin 1493 F pulseaudio /dev/snd/controlC1: devin 1493 F pulseaudio /dev/snd/pcmC1D0c: devin 1493 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Apr 21 23:45:51 2019 InstallationDate: Installed on 2019-04-21 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Right Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Digital clip or distortion, or "overdriven" sound Title: [X555LJ, Realtek ALC3236, Black Headphone Out, Right] Sound is distorted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/06/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555LJ.602 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555LJ dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX555LJ.602:bd05/06/2016:svnASUSTeKCOMPUTERINC.:pnX555LJ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555LJ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X555LJ dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1825739/+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 1825739] Re: [X555LJ, Realtek ALC3236, Black Headphone Out, Right] Sound is distorted
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1825739 Title: [X555LJ, Realtek ALC3236, Black Headphone Out, Right] Sound is distorted Status in alsa-driver package in Ubuntu: Expired Status in linux package in Ubuntu: Expired Bug description: I can hear songs okay with my speaker in laptop, but when i connect headphone in to 3.5mm jack in laptop I hear songs with crackling sound. I'm dual booting with windows. My headphones works fine in windows 10 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: devin 1493 F pulseaudio /dev/snd/controlC1: devin 1493 F pulseaudio /dev/snd/pcmC1D0c: devin 1493 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Apr 21 23:45:51 2019 InstallationDate: Installed on 2019-04-21 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Right Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Digital clip or distortion, or "overdriven" sound Title: [X555LJ, Realtek ALC3236, Black Headphone Out, Right] Sound is distorted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/06/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555LJ.602 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555LJ dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX555LJ.602:bd05/06/2016:svnASUSTeKCOMPUTERINC.:pnX555LJ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555LJ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X555LJ dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1825739/+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 1778322] Re: gvfs-smb-browse can't browse samba/smb tree
** Tags removed: browse browsing verification-needed -- 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/1778322 Title: gvfs-smb-browse can't browse samba/smb tree Status in gvfs: Unknown Status in samba: Unknown Status in gvfs package in Ubuntu: Fix Released Status in samba package in Ubuntu: Fix Released Status in gvfs source package in Bionic: Fix Committed Status in samba source package in Bionic: Fix Released Status in gvfs source package in Cosmic: Fix Committed Status in samba source package in Cosmic: Fix Released Bug description: [Impact] The so called "browsing a windows network" made use of an SMB1 protocol version feature. Recent versions of samba, including the one released with bionic, default to a higher versions of the protocol which lacks this feature. As a result, the "other locations -> windows network" tab in Nautilus is empty even when there are windows or samba machines in the network. Accessing such machines directly, via smb:/// type urls, continues to work. The fix is two-fold: - introduce a new samba API call that can be used to set the protocol version to use - change applications to make use of this API call to set the protocol versio to SMB1/NT1 just for the network browsing gvfs was updated to make use of this api call, if detected at build time. To complete this SRU, gvfs needs a no-change rebuild *after* samba was accepted into proposed. [Test case] * Launch a bionic desktop vm. You can start with a server one, and then install the "ubuntu-desktop" package. In the same command, also install the packages we need for this test: $ sudo apt update $ sudo apt install ubuntu-desktop samba smbclient * set a password for the ubuntu user, so you can login at the graphical console $ sudo passwd ubuntu * set the same password for the ubuntu samba user: sudo smbpasswd -a ubuntu * add a simple [pub] share to samba: $ printf "[pub]\n\tpath=/tmp\n\tguest ok = no\n" | sudo tee -a /etc/samba/smb.conf * reboot $ sudo reboot * login at the graphical console as the ubuntu user. Go through the first-user-setup motions as you want. * try to browse the windows network via "other locations -> windows network". You will get an empty folder. * update the samba and gvfs packages * logout and login again on the gui, browse the windows network again. This time it will show the "WORKGROUP" folder, and if you click through, you will see yourself (your VM) and the [pub] share, among others. * click on the "pub" share, select registered user and login with the ubuntu credentials you created earlier with smbpasswd. * in another terminal, run this command to confirm that the SMB protocol version that was used to connect to [pub] was not just NT1/SMB1, but higher: $ sudo smbstatus ... 8779ubuntu ubuntu 192.168.122.94 (ipv4:192.168.122.94:60818) SMB3_11 -partial(AES-128-CMAC) Note "SMB3_11" above. [Regression potential] The samba update itself just introduces and exposes a new API call. It's up to other applications to make use of that. gvfs was patched to detect this call at build time and use it if it's detected. Packages that are not rebuilt will not see the change, and packages that *are* rebuilt will only see the change if they make use of it. [Other Info] This update introduces a specific runtime dependency between gvfs and libsmbclient due to the new API call added to the latter. Any package that is rebuilt with libsmbclient and makes use of that API call will get this specific dependency. This is handled automatically by dh_mkshlibs. To complete this SRU, gvfs will need a no-change rebuild after samba was accepted into proposed. Disco's gvfs is already using the new call, as can be seen in this build log https://launchpadlibrarian.net/415424052/buildlog_ubuntu-disco-amd64.gvfs_1.40.0-1_BUILDING.txt.gz: ... Dependency smbclient found: YES 0.5.0 Checking for function "smbc_setOptionProtocols" with dependency smbclient: YES The smbc_setOptionProtocols() call is only used when the url is like "smb:///", or the server cannot be resolved. The downgrade overrides the setting in smb.conf, and is used just for this case: browsing the network. When connecting to a machine, the url is like "smb:///", and then this function we are adding is not called. I updated the test to actually click on the machine that shows up in the network browsing, and then check with "smbstatus" which version of the protocol was used when connecting to an actual share. --- Nautilus should show smbtree and host on the smb network. When inputing this command: killall gvfsd-smb-browse && GVFS_DEBUG=1 /usr/lib/gvfs/gvfsd-smb-browse You can see the error: smb-network: Queued new job 0x55b19a2c9f40
[Desktop-packages] [Bug 1833652] Re: [SB-XFi - Creative X-Fi, playback] No sound at all
Made sure everything is on/not muted and still no sound. Also tried under a live session of Ubuntu 16.04 which detected the card, but still came up with no sound. -- 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/1833652 Title: [SB-XFi - Creative X-Fi, playback] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: Installed a new X-Fi sound card, but no audio is being heard during playback on Ubuntu 18.04. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-22-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jfilingeri 1723 F pulseaudio jfilingeri 3577 F alsamixer /dev/snd/controlC1: jfilingeri 1723 F pulseaudio CurrentDesktop: MATE Date: Thu Jun 20 23:32:37 2019 InstallationDate: Installed on 2019-06-18 (3 days ago) InstallationMedia: Ubuntu-MATE 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:XFi failed Symptom_Card: Cedar HDMI Audio [Radeon HD 5400/6300/7300 Series] - HDA ATI HDMI Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jfilingeri 1723 F pulseaudio jfilingeri 3577 F alsamixer /dev/snd/pcmC0D0p: jfilingeri 1723 F...m pulseaudio /dev/snd/controlC1: jfilingeri 1723 F pulseaudio Symptom_Type: No sound at all Title: [SB-XFi - Creative X-Fi, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/08/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F3 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z170M-D3H-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF3:bd09/08/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170M-D3H-CF:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1833652/+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 1833798] [NEW] no restore after update when multiple profiles in use
Public bug reported: When Firefox is ready to force use of a new update, it displays in a tab a message: "Sorry. We just need to do one small thing to keep going. Firefox has just been updated in the background. Click Restart Firefox to complete the update. We will restore all your pages, windows and tabs afterwards, so you can be on your way quickly." However when I am using multiple profiles concurrently, after I click on the "Restart Firefox" button, a window for the profile that received the message does not get restarted after it has been closed and the update for that profile activated. Instead the profile has to be restarted manually as do all of the tabs that were open at the time in that profile. (Note: I typically get this message one profile at a time. The other open profiles are not immediately affected.) I expected that Firefox would restore the one window for the profile that was closed and restore all of the tabs to their previous URL, if not their previous state. Most recently this happened to me as Firefox started updating from 67.0.2 to 67.0.3, but it has been a problem with earlier versions as well. Unfortunately, because this is initiated by the availability of a new Firefox update, I do not have instructions on how to reproduce this problem on demand. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: firefox 67.0.3+build1-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 Uname: Linux 4.15.0-51-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: circ 2588 F pulseaudio /dev/snd/controlC0: circ 2588 F pulseaudio /dev/snd/pcmC2D0p: circ 2588 F...m pulseaudio /dev/snd/controlC2: circ 2588 F pulseaudio BuildID: 20190618131358 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Fri Jun 21 17:36:55 2019 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:1151 DefaultProfilePrefSources: prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-11-11 (222 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IpRoute: default via 192.168.3.1 dev enp3s0 proto dhcp metric 100 169.254.0.0/16 dev enp3s0 scope link metric 1000 192.168.3.0/24 dev enp3s0 proto kernel scope link src 192.168.3.181 metric 100 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Profile1Extensions: extensions.sqlite corrupt or missing Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile1Locales: extensions.sqlite corrupt or missing Profile1PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:1151 Profile1PrefSources: prefs.js Profile1Themes: extensions.sqlite corrupt or missing Profile2Extensions: extensions.sqlite corrupt or missing Profile2IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile2Locales: extensions.sqlite corrupt or missing Profile2PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:1151 Profile2PrefSources: prefs.js Profile2Themes: extensions.sqlite corrupt or missing Profile3Extensions: extensions.sqlite corrupt or missing Profile3IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile3Locales: extensions.sqlite corrupt or missing Profile3PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:1151 Profile3PrefSources: prefs.js Profile3Themes: extensions.sqlite corrupt or missing Profile4Extensions: extensions.sqlite corrupt or missing Profile4IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile4Locales: extensions.sqlite corrupt or missing Profile4PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:1151 Profile4PrefSources: prefs.js Profile4Themes: extensions.sqlite corrupt or missing Profile5Extensions: extensions.sqlite corrupt or missing Profile5IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile5Locales: extensions.sqlite corrupt or missing Profile5PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:1151
[Desktop-packages] [Bug 1833793] Re: Updating to 19.04 audio keeps clicking when it should be silent
** Package changed: ubuntu => alsa-driver (Ubuntu) ** Summary changed: - Updating to 19.04 audio keeps clicking when it should be silent + Updating to 19.04 audio keeps clicking when nothing is playing audio ** Description changed: My Ubuntu version: Ubuntu 19.04 My sound card: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 02) What I expect to happen: Sound is absolutely quiet when no audio is playing What happens now: - Audio output starts clicking every second incredibly annoyingly and loud. + Audio output starts clicking every second incredibly annoyingly and loud. What previously happened on Ubuntu 18.10: - I heard the click twice during boot and then it worked properly (without clicking all the time) + I heard the click twice during boot and then it worked properly (without clicking during the time it should have been silent the time) ** Description changed: My Ubuntu version: Ubuntu 19.04 My sound card: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 02) What I expect to happen: Sound is absolutely quiet when no audio is playing What happens now: Audio output starts clicking every second incredibly annoyingly and loud. What previously happened on Ubuntu 18.10: - I heard the click twice during boot and then it worked properly (without clicking during the time it should have been silent the time) + I heard the click twice during boot and then it worked properly (without clicking during the time it should have been silent) -- 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/1833793 Title: Updating to 19.04 audio keeps clicking when nothing is playing audio Status in alsa-driver package in Ubuntu: New Bug description: My Ubuntu version: Ubuntu 19.04 My sound card: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 02) What I expect to happen: Sound is absolutely quiet when no audio is playing What happens now: Audio output starts clicking every second incredibly annoyingly and loud. What previously happened on Ubuntu 18.10: I heard the click twice during boot and then it worked properly (without clicking during the time it should have been silent) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1833793/+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 1833793] [NEW] Updating to 19.04 audio keeps clicking when it should be silent
You have been subscribed to a public bug: My Ubuntu version: Ubuntu 19.04 My sound card: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 02) What I expect to happen: Sound is absolutely quiet when no audio is playing What happens now: Audio output starts clicking every second incredibly annoyingly and loud. What previously happened on Ubuntu 18.10: I heard the click twice during boot and then it worked properly (without clicking all the time) ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: audio bot-comment -- Updating to 19.04 audio keeps clicking when it should be silent https://bugs.launchpad.net/bugs/1833793 You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. -- 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 1778322] Re: gvfs-smb-browse can't browse samba/smb tree
Can we also get this bug marked as Disco to? Not just Bionic and Cosmic? I'm _still_ getting the issue with a fully updated Disco (19.04). -- 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/1778322 Title: gvfs-smb-browse can't browse samba/smb tree Status in gvfs: Unknown Status in samba: Unknown Status in gvfs package in Ubuntu: Fix Released Status in samba package in Ubuntu: Fix Released Status in gvfs source package in Bionic: Fix Committed Status in samba source package in Bionic: Fix Released Status in gvfs source package in Cosmic: Fix Committed Status in samba source package in Cosmic: Fix Released Bug description: [Impact] The so called "browsing a windows network" made use of an SMB1 protocol version feature. Recent versions of samba, including the one released with bionic, default to a higher versions of the protocol which lacks this feature. As a result, the "other locations -> windows network" tab in Nautilus is empty even when there are windows or samba machines in the network. Accessing such machines directly, via smb:/// type urls, continues to work. The fix is two-fold: - introduce a new samba API call that can be used to set the protocol version to use - change applications to make use of this API call to set the protocol versio to SMB1/NT1 just for the network browsing gvfs was updated to make use of this api call, if detected at build time. To complete this SRU, gvfs needs a no-change rebuild *after* samba was accepted into proposed. [Test case] * Launch a bionic desktop vm. You can start with a server one, and then install the "ubuntu-desktop" package. In the same command, also install the packages we need for this test: $ sudo apt update $ sudo apt install ubuntu-desktop samba smbclient * set a password for the ubuntu user, so you can login at the graphical console $ sudo passwd ubuntu * set the same password for the ubuntu samba user: sudo smbpasswd -a ubuntu * add a simple [pub] share to samba: $ printf "[pub]\n\tpath=/tmp\n\tguest ok = no\n" | sudo tee -a /etc/samba/smb.conf * reboot $ sudo reboot * login at the graphical console as the ubuntu user. Go through the first-user-setup motions as you want. * try to browse the windows network via "other locations -> windows network". You will get an empty folder. * update the samba and gvfs packages * logout and login again on the gui, browse the windows network again. This time it will show the "WORKGROUP" folder, and if you click through, you will see yourself (your VM) and the [pub] share, among others. * click on the "pub" share, select registered user and login with the ubuntu credentials you created earlier with smbpasswd. * in another terminal, run this command to confirm that the SMB protocol version that was used to connect to [pub] was not just NT1/SMB1, but higher: $ sudo smbstatus ... 8779ubuntu ubuntu 192.168.122.94 (ipv4:192.168.122.94:60818) SMB3_11 -partial(AES-128-CMAC) Note "SMB3_11" above. [Regression potential] The samba update itself just introduces and exposes a new API call. It's up to other applications to make use of that. gvfs was patched to detect this call at build time and use it if it's detected. Packages that are not rebuilt will not see the change, and packages that *are* rebuilt will only see the change if they make use of it. [Other Info] This update introduces a specific runtime dependency between gvfs and libsmbclient due to the new API call added to the latter. Any package that is rebuilt with libsmbclient and makes use of that API call will get this specific dependency. This is handled automatically by dh_mkshlibs. To complete this SRU, gvfs will need a no-change rebuild after samba was accepted into proposed. Disco's gvfs is already using the new call, as can be seen in this build log https://launchpadlibrarian.net/415424052/buildlog_ubuntu-disco-amd64.gvfs_1.40.0-1_BUILDING.txt.gz: ... Dependency smbclient found: YES 0.5.0 Checking for function "smbc_setOptionProtocols" with dependency smbclient: YES The smbc_setOptionProtocols() call is only used when the url is like "smb:///", or the server cannot be resolved. The downgrade overrides the setting in smb.conf, and is used just for this case: browsing the network. When connecting to a machine, the url is like "smb:///", and then this function we are adding is not called. I updated the test to actually click on the machine that shows up in the network browsing, and then check with "smbstatus" which version of the protocol was used when connecting to an actual share. --- Nautilus should show smbtree and host on the smb network. When inputing this command: killall gvfsd-smb-browse && GVFS_DEBUG=1
[Desktop-packages] [Bug 1778322] Re: gvfs-smb-browse can't browse samba/smb tree
** Attachment added: "cosmic-populated-windows-network-after-test.png" https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1778322/+attachment/5272233/+files/cosmic-populated-windows-network-after-test.png -- 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/1778322 Title: gvfs-smb-browse can't browse samba/smb tree Status in gvfs: Unknown Status in samba: Unknown Status in gvfs package in Ubuntu: Fix Released Status in samba package in Ubuntu: Fix Released Status in gvfs source package in Bionic: Fix Committed Status in samba source package in Bionic: Fix Released Status in gvfs source package in Cosmic: Fix Committed Status in samba source package in Cosmic: Fix Released Bug description: [Impact] The so called "browsing a windows network" made use of an SMB1 protocol version feature. Recent versions of samba, including the one released with bionic, default to a higher versions of the protocol which lacks this feature. As a result, the "other locations -> windows network" tab in Nautilus is empty even when there are windows or samba machines in the network. Accessing such machines directly, via smb:/// type urls, continues to work. The fix is two-fold: - introduce a new samba API call that can be used to set the protocol version to use - change applications to make use of this API call to set the protocol versio to SMB1/NT1 just for the network browsing gvfs was updated to make use of this api call, if detected at build time. To complete this SRU, gvfs needs a no-change rebuild *after* samba was accepted into proposed. [Test case] * Launch a bionic desktop vm. You can start with a server one, and then install the "ubuntu-desktop" package. In the same command, also install the packages we need for this test: $ sudo apt update $ sudo apt install ubuntu-desktop samba smbclient * set a password for the ubuntu user, so you can login at the graphical console $ sudo passwd ubuntu * set the same password for the ubuntu samba user: sudo smbpasswd -a ubuntu * add a simple [pub] share to samba: $ printf "[pub]\n\tpath=/tmp\n\tguest ok = no\n" | sudo tee -a /etc/samba/smb.conf * reboot $ sudo reboot * login at the graphical console as the ubuntu user. Go through the first-user-setup motions as you want. * try to browse the windows network via "other locations -> windows network". You will get an empty folder. * update the samba and gvfs packages * logout and login again on the gui, browse the windows network again. This time it will show the "WORKGROUP" folder, and if you click through, you will see yourself (your VM) and the [pub] share, among others. * click on the "pub" share, select registered user and login with the ubuntu credentials you created earlier with smbpasswd. * in another terminal, run this command to confirm that the SMB protocol version that was used to connect to [pub] was not just NT1/SMB1, but higher: $ sudo smbstatus ... 8779ubuntu ubuntu 192.168.122.94 (ipv4:192.168.122.94:60818) SMB3_11 -partial(AES-128-CMAC) Note "SMB3_11" above. [Regression potential] The samba update itself just introduces and exposes a new API call. It's up to other applications to make use of that. gvfs was patched to detect this call at build time and use it if it's detected. Packages that are not rebuilt will not see the change, and packages that *are* rebuilt will only see the change if they make use of it. [Other Info] This update introduces a specific runtime dependency between gvfs and libsmbclient due to the new API call added to the latter. Any package that is rebuilt with libsmbclient and makes use of that API call will get this specific dependency. This is handled automatically by dh_mkshlibs. To complete this SRU, gvfs will need a no-change rebuild after samba was accepted into proposed. Disco's gvfs is already using the new call, as can be seen in this build log https://launchpadlibrarian.net/415424052/buildlog_ubuntu-disco-amd64.gvfs_1.40.0-1_BUILDING.txt.gz: ... Dependency smbclient found: YES 0.5.0 Checking for function "smbc_setOptionProtocols" with dependency smbclient: YES The smbc_setOptionProtocols() call is only used when the url is like "smb:///", or the server cannot be resolved. The downgrade overrides the setting in smb.conf, and is used just for this case: browsing the network. When connecting to a machine, the url is like "smb:///", and then this function we are adding is not called. I updated the test to actually click on the machine that shows up in the network browsing, and then check with "smbstatus" which version of the protocol was used when connecting to an actual share. --- Nautilus should show smbtree and host on the smb network. When inputing this command:
[Desktop-packages] [Bug 1778322] Re: gvfs-smb-browse can't browse samba/smb tree
Cosmic verification First reproducing the bug with these packages: Version table: *** 1.38.1-0ubuntu1.2 500 500 http://br.archive.ubuntu.com/ubuntu cosmic-updates/main amd64 Packages windows network tab is empty (see screenshot cosmic-empty-windows-network-before-test.png) Now with these packages: *** 1.38.1-0ubuntu1.3.1 500 500 http://br.archive.ubuntu.com/ubuntu cosmic-proposed/main amd64 Packages After a logout and new login, the windows network tab is populated (see cosmic-populated-windows-network-after-test.png) and I can connect to the displayed pub share (see cosmic-connecting-to-pub-after-test.png). After I'm connected, smbstatus shows that smb3.11 was used for the connection to pub: ubuntu@cosmic-desktop:~$ sudo smbstatus Samba version 4.8.4-Ubuntu PID Username GroupMachine Protocol Version Encryption Signing 5812nobody nogroup cosmic-desktop (ipv4:192.168.122.27:57330) NT1 -- 5821nobody nogroup cosmic-desktop (ipv4:192.168.122.27:57334) NT1 -- 5880ubuntu ubuntu 192.168.122.27 (ipv4:192.168.122.27:47898) SMB3_11 -partial(AES-128-CMAC) 5828nobody nogroup cosmic-desktop (ipv4:192.168.122.27:57336) NT1 -- Service pid Machine Connected at Encryption Signing - IPC$ 5828cosmic-desktop Fri Jun 21 21:36:38 2019 UTC - - IPC$ 5812cosmic-desktop Fri Jun 21 21:36:18 2019 UTC - - pub 5880192.168.122.27 Fri Jun 21 21:37:00 2019 UTC - - IPC$ 5821cosmic-desktop Fri Jun 21 21:36:21 2019 UTC - - No locked files As stated in the bionic verification, a fix for https://bugs.launchpad.net/gvfs/+bug/1828107 is still relevant. cosmic verification succeeded. -- 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/1778322 Title: gvfs-smb-browse can't browse samba/smb tree Status in gvfs: Unknown Status in samba: Unknown Status in gvfs package in Ubuntu: Fix Released Status in samba package in Ubuntu: Fix Released Status in gvfs source package in Bionic: Fix Committed Status in samba source package in Bionic: Fix Released Status in gvfs source package in Cosmic: Fix Committed Status in samba source package in Cosmic: Fix Released Bug description: [Impact] The so called "browsing a windows network" made use of an SMB1 protocol version feature. Recent versions of samba, including the one released with bionic, default to a higher versions of the protocol which lacks this feature. As a result, the "other locations -> windows network" tab in Nautilus is empty even when there are windows or samba machines in the network. Accessing such machines directly, via smb:/// type urls, continues to work. The fix is two-fold: - introduce a new samba API call that can be used to set the protocol version to use - change applications to make use of this API call to set the protocol versio to SMB1/NT1 just for the network browsing gvfs was updated to make use of this api call, if detected at build time. To complete this SRU, gvfs needs a no-change rebuild *after* samba was accepted into proposed. [Test case] * Launch a bionic desktop vm. You can start with a server one, and then install the "ubuntu-desktop" package. In the same command, also install the packages we need for this test: $ sudo apt update $ sudo apt install ubuntu-desktop samba smbclient * set a password for the ubuntu user, so you can login at the graphical console $ sudo passwd ubuntu * set the same password for the ubuntu samba user: sudo smbpasswd -a ubuntu * add a simple [pub] share to samba: $ printf "[pub]\n\tpath=/tmp\n\tguest ok = no\n" | sudo tee -a /etc/samba/smb.conf * reboot $ sudo reboot * login at the graphical console as the ubuntu user. Go through the first-user-setup motions as you want. * try to browse the windows network via "other locations -> windows network". You will get an empty folder. * update the samba and gvfs packages * logout and login again on the gui, browse the windows network again. This time it will show the "WORKGROUP" folder, and if you click through, you will see yourself (your VM) and the [pub] share, among others. * click on the "pub" share, select
[Desktop-packages] [Bug 1778322] Re: gvfs-smb-browse can't browse samba/smb tree
** Attachment added: "cosmic-connecting-to-pub-after-test.png" https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1778322/+attachment/5272234/+files/cosmic-connecting-to-pub-after-test.png ** Tags removed: verification-needed-cosmic ** Tags added: verification-done-cosmic -- 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/1778322 Title: gvfs-smb-browse can't browse samba/smb tree Status in gvfs: Unknown Status in samba: Unknown Status in gvfs package in Ubuntu: Fix Released Status in samba package in Ubuntu: Fix Released Status in gvfs source package in Bionic: Fix Committed Status in samba source package in Bionic: Fix Released Status in gvfs source package in Cosmic: Fix Committed Status in samba source package in Cosmic: Fix Released Bug description: [Impact] The so called "browsing a windows network" made use of an SMB1 protocol version feature. Recent versions of samba, including the one released with bionic, default to a higher versions of the protocol which lacks this feature. As a result, the "other locations -> windows network" tab in Nautilus is empty even when there are windows or samba machines in the network. Accessing such machines directly, via smb:/// type urls, continues to work. The fix is two-fold: - introduce a new samba API call that can be used to set the protocol version to use - change applications to make use of this API call to set the protocol versio to SMB1/NT1 just for the network browsing gvfs was updated to make use of this api call, if detected at build time. To complete this SRU, gvfs needs a no-change rebuild *after* samba was accepted into proposed. [Test case] * Launch a bionic desktop vm. You can start with a server one, and then install the "ubuntu-desktop" package. In the same command, also install the packages we need for this test: $ sudo apt update $ sudo apt install ubuntu-desktop samba smbclient * set a password for the ubuntu user, so you can login at the graphical console $ sudo passwd ubuntu * set the same password for the ubuntu samba user: sudo smbpasswd -a ubuntu * add a simple [pub] share to samba: $ printf "[pub]\n\tpath=/tmp\n\tguest ok = no\n" | sudo tee -a /etc/samba/smb.conf * reboot $ sudo reboot * login at the graphical console as the ubuntu user. Go through the first-user-setup motions as you want. * try to browse the windows network via "other locations -> windows network". You will get an empty folder. * update the samba and gvfs packages * logout and login again on the gui, browse the windows network again. This time it will show the "WORKGROUP" folder, and if you click through, you will see yourself (your VM) and the [pub] share, among others. * click on the "pub" share, select registered user and login with the ubuntu credentials you created earlier with smbpasswd. * in another terminal, run this command to confirm that the SMB protocol version that was used to connect to [pub] was not just NT1/SMB1, but higher: $ sudo smbstatus ... 8779ubuntu ubuntu 192.168.122.94 (ipv4:192.168.122.94:60818) SMB3_11 -partial(AES-128-CMAC) Note "SMB3_11" above. [Regression potential] The samba update itself just introduces and exposes a new API call. It's up to other applications to make use of that. gvfs was patched to detect this call at build time and use it if it's detected. Packages that are not rebuilt will not see the change, and packages that *are* rebuilt will only see the change if they make use of it. [Other Info] This update introduces a specific runtime dependency between gvfs and libsmbclient due to the new API call added to the latter. Any package that is rebuilt with libsmbclient and makes use of that API call will get this specific dependency. This is handled automatically by dh_mkshlibs. To complete this SRU, gvfs will need a no-change rebuild after samba was accepted into proposed. Disco's gvfs is already using the new call, as can be seen in this build log https://launchpadlibrarian.net/415424052/buildlog_ubuntu-disco-amd64.gvfs_1.40.0-1_BUILDING.txt.gz: ... Dependency smbclient found: YES 0.5.0 Checking for function "smbc_setOptionProtocols" with dependency smbclient: YES The smbc_setOptionProtocols() call is only used when the url is like "smb:///", or the server cannot be resolved. The downgrade overrides the setting in smb.conf, and is used just for this case: browsing the network. When connecting to a machine, the url is like "smb:///", and then this function we are adding is not called. I updated the test to actually click on the machine that shows up in the network browsing, and then check with "smbstatus" which version of the protocol was used when connecting to an actual share. --- Nautilus should show
[Desktop-packages] [Bug 1778322] Re: gvfs-smb-browse can't browse samba/smb tree
** Attachment added: "cosmic-empty-windows-network-before-test.png" https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1778322/+attachment/5272232/+files/cosmic-empty-windows-network-before-test.png -- 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/1778322 Title: gvfs-smb-browse can't browse samba/smb tree Status in gvfs: Unknown Status in samba: Unknown Status in gvfs package in Ubuntu: Fix Released Status in samba package in Ubuntu: Fix Released Status in gvfs source package in Bionic: Fix Committed Status in samba source package in Bionic: Fix Released Status in gvfs source package in Cosmic: Fix Committed Status in samba source package in Cosmic: Fix Released Bug description: [Impact] The so called "browsing a windows network" made use of an SMB1 protocol version feature. Recent versions of samba, including the one released with bionic, default to a higher versions of the protocol which lacks this feature. As a result, the "other locations -> windows network" tab in Nautilus is empty even when there are windows or samba machines in the network. Accessing such machines directly, via smb:/// type urls, continues to work. The fix is two-fold: - introduce a new samba API call that can be used to set the protocol version to use - change applications to make use of this API call to set the protocol versio to SMB1/NT1 just for the network browsing gvfs was updated to make use of this api call, if detected at build time. To complete this SRU, gvfs needs a no-change rebuild *after* samba was accepted into proposed. [Test case] * Launch a bionic desktop vm. You can start with a server one, and then install the "ubuntu-desktop" package. In the same command, also install the packages we need for this test: $ sudo apt update $ sudo apt install ubuntu-desktop samba smbclient * set a password for the ubuntu user, so you can login at the graphical console $ sudo passwd ubuntu * set the same password for the ubuntu samba user: sudo smbpasswd -a ubuntu * add a simple [pub] share to samba: $ printf "[pub]\n\tpath=/tmp\n\tguest ok = no\n" | sudo tee -a /etc/samba/smb.conf * reboot $ sudo reboot * login at the graphical console as the ubuntu user. Go through the first-user-setup motions as you want. * try to browse the windows network via "other locations -> windows network". You will get an empty folder. * update the samba and gvfs packages * logout and login again on the gui, browse the windows network again. This time it will show the "WORKGROUP" folder, and if you click through, you will see yourself (your VM) and the [pub] share, among others. * click on the "pub" share, select registered user and login with the ubuntu credentials you created earlier with smbpasswd. * in another terminal, run this command to confirm that the SMB protocol version that was used to connect to [pub] was not just NT1/SMB1, but higher: $ sudo smbstatus ... 8779ubuntu ubuntu 192.168.122.94 (ipv4:192.168.122.94:60818) SMB3_11 -partial(AES-128-CMAC) Note "SMB3_11" above. [Regression potential] The samba update itself just introduces and exposes a new API call. It's up to other applications to make use of that. gvfs was patched to detect this call at build time and use it if it's detected. Packages that are not rebuilt will not see the change, and packages that *are* rebuilt will only see the change if they make use of it. [Other Info] This update introduces a specific runtime dependency between gvfs and libsmbclient due to the new API call added to the latter. Any package that is rebuilt with libsmbclient and makes use of that API call will get this specific dependency. This is handled automatically by dh_mkshlibs. To complete this SRU, gvfs will need a no-change rebuild after samba was accepted into proposed. Disco's gvfs is already using the new call, as can be seen in this build log https://launchpadlibrarian.net/415424052/buildlog_ubuntu-disco-amd64.gvfs_1.40.0-1_BUILDING.txt.gz: ... Dependency smbclient found: YES 0.5.0 Checking for function "smbc_setOptionProtocols" with dependency smbclient: YES The smbc_setOptionProtocols() call is only used when the url is like "smb:///", or the server cannot be resolved. The downgrade overrides the setting in smb.conf, and is used just for this case: browsing the network. When connecting to a machine, the url is like "smb:///", and then this function we are adding is not called. I updated the test to actually click on the machine that shows up in the network browsing, and then check with "smbstatus" which version of the protocol was used when connecting to an actual share. --- Nautilus should show smbtree and host on the smb network. When inputing this command:
[Desktop-packages] [Bug 1778322] Re: gvfs-smb-browse can't browse samba/smb tree
** Attachment added: "populated-windows-network-after-test.png" https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1778322/+attachment/5272226/+files/populated-windows-network-after-test.png -- 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/1778322 Title: gvfs-smb-browse can't browse samba/smb tree Status in gvfs: Unknown Status in samba: Unknown Status in gvfs package in Ubuntu: Fix Released Status in samba package in Ubuntu: Fix Released Status in gvfs source package in Bionic: Fix Committed Status in samba source package in Bionic: Fix Released Status in gvfs source package in Cosmic: Fix Committed Status in samba source package in Cosmic: Fix Released Bug description: [Impact] The so called "browsing a windows network" made use of an SMB1 protocol version feature. Recent versions of samba, including the one released with bionic, default to a higher versions of the protocol which lacks this feature. As a result, the "other locations -> windows network" tab in Nautilus is empty even when there are windows or samba machines in the network. Accessing such machines directly, via smb:/// type urls, continues to work. The fix is two-fold: - introduce a new samba API call that can be used to set the protocol version to use - change applications to make use of this API call to set the protocol versio to SMB1/NT1 just for the network browsing gvfs was updated to make use of this api call, if detected at build time. To complete this SRU, gvfs needs a no-change rebuild *after* samba was accepted into proposed. [Test case] * Launch a bionic desktop vm. You can start with a server one, and then install the "ubuntu-desktop" package. In the same command, also install the packages we need for this test: $ sudo apt update $ sudo apt install ubuntu-desktop samba smbclient * set a password for the ubuntu user, so you can login at the graphical console $ sudo passwd ubuntu * set the same password for the ubuntu samba user: sudo smbpasswd -a ubuntu * add a simple [pub] share to samba: $ printf "[pub]\n\tpath=/tmp\n\tguest ok = no\n" | sudo tee -a /etc/samba/smb.conf * reboot $ sudo reboot * login at the graphical console as the ubuntu user. Go through the first-user-setup motions as you want. * try to browse the windows network via "other locations -> windows network". You will get an empty folder. * update the samba and gvfs packages * logout and login again on the gui, browse the windows network again. This time it will show the "WORKGROUP" folder, and if you click through, you will see yourself (your VM) and the [pub] share, among others. * click on the "pub" share, select registered user and login with the ubuntu credentials you created earlier with smbpasswd. * in another terminal, run this command to confirm that the SMB protocol version that was used to connect to [pub] was not just NT1/SMB1, but higher: $ sudo smbstatus ... 8779ubuntu ubuntu 192.168.122.94 (ipv4:192.168.122.94:60818) SMB3_11 -partial(AES-128-CMAC) Note "SMB3_11" above. [Regression potential] The samba update itself just introduces and exposes a new API call. It's up to other applications to make use of that. gvfs was patched to detect this call at build time and use it if it's detected. Packages that are not rebuilt will not see the change, and packages that *are* rebuilt will only see the change if they make use of it. [Other Info] This update introduces a specific runtime dependency between gvfs and libsmbclient due to the new API call added to the latter. Any package that is rebuilt with libsmbclient and makes use of that API call will get this specific dependency. This is handled automatically by dh_mkshlibs. To complete this SRU, gvfs will need a no-change rebuild after samba was accepted into proposed. Disco's gvfs is already using the new call, as can be seen in this build log https://launchpadlibrarian.net/415424052/buildlog_ubuntu-disco-amd64.gvfs_1.40.0-1_BUILDING.txt.gz: ... Dependency smbclient found: YES 0.5.0 Checking for function "smbc_setOptionProtocols" with dependency smbclient: YES The smbc_setOptionProtocols() call is only used when the url is like "smb:///", or the server cannot be resolved. The downgrade overrides the setting in smb.conf, and is used just for this case: browsing the network. When connecting to a machine, the url is like "smb:///", and then this function we are adding is not called. I updated the test to actually click on the machine that shows up in the network browsing, and then check with "smbstatus" which version of the protocol was used when connecting to an actual share. --- Nautilus should show smbtree and host on the smb network. When inputing this command: killall
[Desktop-packages] [Bug 1778322] Re: gvfs-smb-browse can't browse samba/smb tree
Bionic desktop verification With gvfs-backends from the release pocket: ubuntu@bionic-desktop:~$ apt-cache policy gvfs-backends gvfs-backends: Installed: 1.36.1-0ubuntu1.3 Candidate: 1.36.1-0ubuntu1.3 Version table: *** 1.36.1-0ubuntu1.3 500 500 http://br.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages I get an empty "windows network" tab in the desktop (see attached screenshot empty-windows-network-before-test.png). After updating to this package from proposed: Version table: *** 1.36.1-0ubuntu1.3.2 500 500 http://br.archive.ubuntu.com/ubuntu bionic-proposed/main amd64 Packages And logging out and back in, I get a populated windows network tab (see screenshot populated-windows-network-after-test.png). I can then connect to the pub share on localhost (see screenshot connecting-to-pub-after-test.png) and, once that is done, smbstatus shows this output: ubuntu@bionic-desktop:~$ sudo smbstatus Samba version 4.7.6-Ubuntu PID Username GroupMachine Protocol Version Encryption Signing 3771nobody nogroup bionic-desktop (ipv4:192.168.122.213:56026) NT1 -- 3874ubuntu ubuntu 192.168.122.213 (ipv4:192.168.122.213:32800) SMB3_11 -partial(AES-128-CMAC) 3807nobody nogroup bionic-desktop (ipv4:192.168.122.213:56028) NT1 -- 3762nobody nogroup bionic-desktop (ipv4:192.168.122.213:56022) NT1 -- Service pid Machine Connected at Encryption Signing - IPC$ 3762bionic-desktop Fri Jun 21 21:07:33 2019 UTC - - IPC$ 3807bionic-desktop Fri Jun 21 21:08:09 2019 UTC - - IPC$ 3771bionic-desktop Fri Jun 21 21:07:37 2019 UTC - - pub 3874192.168.122.213 Fri Jun 21 21:08:30 2019 UTC - - No locked files The connection to the pub share is using SMB3_11. The connections using NT1 show why https://bugs.launchpad.net/gvfs/+bug/1828107 is still relevant, but it's a separate bug. See comment #55 for my reasoning. I think releasing this update is a step in the right direction. Bionic verification succeeded. -- 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/1778322 Title: gvfs-smb-browse can't browse samba/smb tree Status in gvfs: Unknown Status in samba: Unknown Status in gvfs package in Ubuntu: Fix Released Status in samba package in Ubuntu: Fix Released Status in gvfs source package in Bionic: Fix Committed Status in samba source package in Bionic: Fix Released Status in gvfs source package in Cosmic: Fix Committed Status in samba source package in Cosmic: Fix Released Bug description: [Impact] The so called "browsing a windows network" made use of an SMB1 protocol version feature. Recent versions of samba, including the one released with bionic, default to a higher versions of the protocol which lacks this feature. As a result, the "other locations -> windows network" tab in Nautilus is empty even when there are windows or samba machines in the network. Accessing such machines directly, via smb:/// type urls, continues to work. The fix is two-fold: - introduce a new samba API call that can be used to set the protocol version to use - change applications to make use of this API call to set the protocol versio to SMB1/NT1 just for the network browsing gvfs was updated to make use of this api call, if detected at build time. To complete this SRU, gvfs needs a no-change rebuild *after* samba was accepted into proposed. [Test case] * Launch a bionic desktop vm. You can start with a server one, and then install the "ubuntu-desktop" package. In the same command, also install the packages we need for this test: $ sudo apt update $ sudo apt install ubuntu-desktop samba smbclient * set a password for the ubuntu user, so you can login at the graphical console $ sudo passwd ubuntu * set the same password for the ubuntu samba user: sudo smbpasswd -a ubuntu * add a simple [pub] share to samba: $ printf "[pub]\n\tpath=/tmp\n\tguest ok = no\n" | sudo tee -a /etc/samba/smb.conf * reboot $ sudo reboot * login at the graphical console as the ubuntu user. Go through the first-user-setup motions as you want. * try to browse the windows network via "other locations ->
[Desktop-packages] [Bug 1778322] Re: gvfs-smb-browse can't browse samba/smb tree
** Attachment added: "connecting-to-pub-after-test.png" https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1778322/+attachment/5272227/+files/connecting-to-pub-after-test.png ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- 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/1778322 Title: gvfs-smb-browse can't browse samba/smb tree Status in gvfs: Unknown Status in samba: Unknown Status in gvfs package in Ubuntu: Fix Released Status in samba package in Ubuntu: Fix Released Status in gvfs source package in Bionic: Fix Committed Status in samba source package in Bionic: Fix Released Status in gvfs source package in Cosmic: Fix Committed Status in samba source package in Cosmic: Fix Released Bug description: [Impact] The so called "browsing a windows network" made use of an SMB1 protocol version feature. Recent versions of samba, including the one released with bionic, default to a higher versions of the protocol which lacks this feature. As a result, the "other locations -> windows network" tab in Nautilus is empty even when there are windows or samba machines in the network. Accessing such machines directly, via smb:/// type urls, continues to work. The fix is two-fold: - introduce a new samba API call that can be used to set the protocol version to use - change applications to make use of this API call to set the protocol versio to SMB1/NT1 just for the network browsing gvfs was updated to make use of this api call, if detected at build time. To complete this SRU, gvfs needs a no-change rebuild *after* samba was accepted into proposed. [Test case] * Launch a bionic desktop vm. You can start with a server one, and then install the "ubuntu-desktop" package. In the same command, also install the packages we need for this test: $ sudo apt update $ sudo apt install ubuntu-desktop samba smbclient * set a password for the ubuntu user, so you can login at the graphical console $ sudo passwd ubuntu * set the same password for the ubuntu samba user: sudo smbpasswd -a ubuntu * add a simple [pub] share to samba: $ printf "[pub]\n\tpath=/tmp\n\tguest ok = no\n" | sudo tee -a /etc/samba/smb.conf * reboot $ sudo reboot * login at the graphical console as the ubuntu user. Go through the first-user-setup motions as you want. * try to browse the windows network via "other locations -> windows network". You will get an empty folder. * update the samba and gvfs packages * logout and login again on the gui, browse the windows network again. This time it will show the "WORKGROUP" folder, and if you click through, you will see yourself (your VM) and the [pub] share, among others. * click on the "pub" share, select registered user and login with the ubuntu credentials you created earlier with smbpasswd. * in another terminal, run this command to confirm that the SMB protocol version that was used to connect to [pub] was not just NT1/SMB1, but higher: $ sudo smbstatus ... 8779ubuntu ubuntu 192.168.122.94 (ipv4:192.168.122.94:60818) SMB3_11 -partial(AES-128-CMAC) Note "SMB3_11" above. [Regression potential] The samba update itself just introduces and exposes a new API call. It's up to other applications to make use of that. gvfs was patched to detect this call at build time and use it if it's detected. Packages that are not rebuilt will not see the change, and packages that *are* rebuilt will only see the change if they make use of it. [Other Info] This update introduces a specific runtime dependency between gvfs and libsmbclient due to the new API call added to the latter. Any package that is rebuilt with libsmbclient and makes use of that API call will get this specific dependency. This is handled automatically by dh_mkshlibs. To complete this SRU, gvfs will need a no-change rebuild after samba was accepted into proposed. Disco's gvfs is already using the new call, as can be seen in this build log https://launchpadlibrarian.net/415424052/buildlog_ubuntu-disco-amd64.gvfs_1.40.0-1_BUILDING.txt.gz: ... Dependency smbclient found: YES 0.5.0 Checking for function "smbc_setOptionProtocols" with dependency smbclient: YES The smbc_setOptionProtocols() call is only used when the url is like "smb:///", or the server cannot be resolved. The downgrade overrides the setting in smb.conf, and is used just for this case: browsing the network. When connecting to a machine, the url is like "smb:///", and then this function we are adding is not called. I updated the test to actually click on the machine that shows up in the network browsing, and then check with "smbstatus" which version of the protocol was used when connecting to an actual share. --- Nautilus should show smbtree and
[Desktop-packages] [Bug 1778322] Re: gvfs-smb-browse can't browse samba/smb tree
** Attachment added: "empty-windows-network-before-test.png" https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1778322/+attachment/5272225/+files/empty-windows-network-before-test.png -- 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/1778322 Title: gvfs-smb-browse can't browse samba/smb tree Status in gvfs: Unknown Status in samba: Unknown Status in gvfs package in Ubuntu: Fix Released Status in samba package in Ubuntu: Fix Released Status in gvfs source package in Bionic: Fix Committed Status in samba source package in Bionic: Fix Released Status in gvfs source package in Cosmic: Fix Committed Status in samba source package in Cosmic: Fix Released Bug description: [Impact] The so called "browsing a windows network" made use of an SMB1 protocol version feature. Recent versions of samba, including the one released with bionic, default to a higher versions of the protocol which lacks this feature. As a result, the "other locations -> windows network" tab in Nautilus is empty even when there are windows or samba machines in the network. Accessing such machines directly, via smb:/// type urls, continues to work. The fix is two-fold: - introduce a new samba API call that can be used to set the protocol version to use - change applications to make use of this API call to set the protocol versio to SMB1/NT1 just for the network browsing gvfs was updated to make use of this api call, if detected at build time. To complete this SRU, gvfs needs a no-change rebuild *after* samba was accepted into proposed. [Test case] * Launch a bionic desktop vm. You can start with a server one, and then install the "ubuntu-desktop" package. In the same command, also install the packages we need for this test: $ sudo apt update $ sudo apt install ubuntu-desktop samba smbclient * set a password for the ubuntu user, so you can login at the graphical console $ sudo passwd ubuntu * set the same password for the ubuntu samba user: sudo smbpasswd -a ubuntu * add a simple [pub] share to samba: $ printf "[pub]\n\tpath=/tmp\n\tguest ok = no\n" | sudo tee -a /etc/samba/smb.conf * reboot $ sudo reboot * login at the graphical console as the ubuntu user. Go through the first-user-setup motions as you want. * try to browse the windows network via "other locations -> windows network". You will get an empty folder. * update the samba and gvfs packages * logout and login again on the gui, browse the windows network again. This time it will show the "WORKGROUP" folder, and if you click through, you will see yourself (your VM) and the [pub] share, among others. * click on the "pub" share, select registered user and login with the ubuntu credentials you created earlier with smbpasswd. * in another terminal, run this command to confirm that the SMB protocol version that was used to connect to [pub] was not just NT1/SMB1, but higher: $ sudo smbstatus ... 8779ubuntu ubuntu 192.168.122.94 (ipv4:192.168.122.94:60818) SMB3_11 -partial(AES-128-CMAC) Note "SMB3_11" above. [Regression potential] The samba update itself just introduces and exposes a new API call. It's up to other applications to make use of that. gvfs was patched to detect this call at build time and use it if it's detected. Packages that are not rebuilt will not see the change, and packages that *are* rebuilt will only see the change if they make use of it. [Other Info] This update introduces a specific runtime dependency between gvfs and libsmbclient due to the new API call added to the latter. Any package that is rebuilt with libsmbclient and makes use of that API call will get this specific dependency. This is handled automatically by dh_mkshlibs. To complete this SRU, gvfs will need a no-change rebuild after samba was accepted into proposed. Disco's gvfs is already using the new call, as can be seen in this build log https://launchpadlibrarian.net/415424052/buildlog_ubuntu-disco-amd64.gvfs_1.40.0-1_BUILDING.txt.gz: ... Dependency smbclient found: YES 0.5.0 Checking for function "smbc_setOptionProtocols" with dependency smbclient: YES The smbc_setOptionProtocols() call is only used when the url is like "smb:///", or the server cannot be resolved. The downgrade overrides the setting in smb.conf, and is used just for this case: browsing the network. When connecting to a machine, the url is like "smb:///", and then this function we are adding is not called. I updated the test to actually click on the machine that shows up in the network browsing, and then check with "smbstatus" which version of the protocol was used when connecting to an actual share. --- Nautilus should show smbtree and host on the smb network. When inputing this command: killall
[Desktop-packages] [Bug 1833197] Re: crashes when creating annotations (Segmentation fault (core dumped))
** Tags added: bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1833197 Title: crashes when creating annotations (Segmentation fault (core dumped)) Status in evince package in Ubuntu: Incomplete Bug description: After creating several annotations in a PDF document evince ends up crashing with an inespecific segfault terminal output. It happens always, but it takes a long time, so it's hard to reproduce, and it doesn't always happens in the same place, despite I've tried to hit the bug reopening and inserting an annotation in the same place. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1833197/+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 1833197] Re: crashes when creating annotations (Segmentation fault (core dumped))
Hi Sebastien, thanks for your prompt reply. I'm in the latest LTS. I don't see any trace of the crash. Maybe it was automatically reported? I think I have it configured that way. I'll try to reproduce it and then go through the instructions in the link, although, as I say, it's hard to reproduce. I just happens after creating annotations for a while. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1833197 Title: crashes when creating annotations (Segmentation fault (core dumped)) Status in evince package in Ubuntu: Incomplete Bug description: After creating several annotations in a PDF document evince ends up crashing with an inespecific segfault terminal output. It happens always, but it takes a long time, so it's hard to reproduce, and it doesn't always happens in the same place, despite I've tried to hit the bug reopening and inserting an annotation in the same place. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1833197/+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 1832436] Re: login page first appears sideways for Lenovo miix 510 ubuntu 18.04 and 18.10
** Also affects: gdm3 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1832436 Title: login page first appears sideways for Lenovo miix 510 ubuntu 18.04 and 18.10 Status in Ubuntu: New Status in gdm3 package in Ubuntu: New Bug description: I have experienced this for ubuntu 18.04 and 18.10 on a Lenovo Miix 510 laptop. This problem is fixed on ubuntu 19.04 The login page appears sideways (the mouse orientation is sideways also). After logging in the screen is corrected. I believe the issue lies with the detection of the accelerometer or perhaps the driver of the accelerometer. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1832436/+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 1809407] Re: [nvidia] Corrupted wallpaper after resuming from suspend
Will this be fixed for disco as well? -- 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/1809407 Title: [nvidia] Corrupted wallpaper after resuming from suspend Status in GNOME Shell: New Status in mutter package in Ubuntu: In Progress Status in mutter source package in Bionic: Confirmed Status in mutter source package in Disco: Confirmed Status in mutter source package in Eoan: In Progress Bug description: https://trello.com/c/i5hENxSO Every other wake from sleep presents a corrupted screen with no unlock app. There's a dock and system menu on a black background with pixel garbage. Some personal information in the dock's large window thumbnails. Bitmap garbage flashes on the screen when interacting with anything. Only workaround is doing another sleep-wake cycle. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Uname: Linux 4.18.0-12-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..4b.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:4b:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.87 Tue Aug 21 12:33:05 PDT 2018 GCC version: gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1) ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Dec 20 22:19:29 2018 DistUpgraded: 2018-12-01 23:07:50,385 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: nvidia, 390.87, 4.18.0-11-generic, x86_64: installed nvidia, 390.87, 4.18.0-12-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-11-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-12-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GP106 [GeForce GTX 1060 3GB] [3842:6162] InstallationDate: Installed on 2018-10-28 (54 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Gigabyte Technology Co., Ltd. Default string ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-12-generic root=UUID=a8c839e7-c579-4699-999a-748f804ff9e0 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to cosmic on 2018-12-02 (18 days ago) dmi.bios.date: 06/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F24 dmi.board.asset.tag: Default string dmi.board.name: X99P-SLI-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.:bvrF24:bd06/08/2017:svnGigabyteTechnologyCo.,Ltd.:pnDefaultstring:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX99P-SLI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Default string dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1809407/+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 1822179] Re: Resuming from sleep breaks desktop and lock screen background in GNOME
*** This bug is a duplicate of bug 1809407 *** https://bugs.launchpad.net/bugs/1809407 Same here for: Ubuntu 19.04 gnome 3.32.0 GPU: Nvidia MX150. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1822179 Title: Resuming from sleep breaks desktop and lock screen background in GNOME Status in gnome-shell package in Ubuntu: Confirmed Bug description: CPU: AMD Ryzen 5 1600 MOBO: MSI B350M MORTAR GPU: NVIDIA GTX 1060 Ubuntu version: 19.04 Nvidia driver version: 418.56 The system is updated with the latest updates as today, 28 March 2019 As the title says, in Ubuntu 19.04 the GNOME lockscreen gets corrupted, and the GNOME desktop has blank background after resuming from standby/sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1822179/+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 1833757] [NEW] PCI/internal sound card not detected
Public bug reported: no audio ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-151.178-generic 4.4.179 Uname: Linux 4.4.0-151-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Sat Jun 22 01:16:52 2019 InstallationDate: Installed on 2019-05-25 (27 days ago) InstallationMedia: It PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: Upgraded to xenial on 2019-05-30 (22 days ago) dmi.bios.date: 06/13/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 8TCN44WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330-15IKB dmi.modalias: dmi:bvnLENOVO:bvr8TCN44WW:bd06/13/2018:svnLENOVO:pn81DE:pvrLenovoideapad330-15IKB:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad330-15IKB: dmi.product.name: 81DE dmi.product.version: Lenovo ideapad 330-15IKB dmi.sys.vendor: LENOVO ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- 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/1833757 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: no audio ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-151.178-generic 4.4.179 Uname: Linux 4.4.0-151-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Sat Jun 22 01:16:52 2019 InstallationDate: Installed on 2019-05-25 (27 days ago) InstallationMedia: It PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: Upgraded to xenial on 2019-05-30 (22 days ago) dmi.bios.date: 06/13/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 8TCN44WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330-15IKB dmi.modalias: dmi:bvnLENOVO:bvr8TCN44WW:bd06/13/2018:svnLENOVO:pn81DE:pvrLenovoideapad330-15IKB:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad330-15IKB: dmi.product.name: 81DE dmi.product.version: Lenovo ideapad 330-15IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1833757/+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 1782535] Re: cifs - poor upload speed with nautilus compared to rsync
** Changed in: glib Status: Unknown => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1782535 Title: cifs - poor upload speed with nautilus compared to rsync Status in GLib: Fix Released Status in glib2.0 package in Ubuntu: Fix Released Bug description: I'm mounting folders from my NAS on my computer (Ubuntu 18.04) with cifs. Copying an 8 GB file... Upload (local -> mounted) - Nautilus/Nemo -> 6 MB/s - rsync -> 50-60 MB/s Download performance is also strange, but not my biggest concern. Download (mounted -> local) - Nautilus/Nemo -> 90 MB/s - rsync -> 50-60 MB/s rsync command (upload): rsync --progress /home/me/file.iso /mnt/cifs_media/ fstab entry: //nas/media /mnt/cifs_media cifs vers=3.0,uid=me,gid=me,credentials=/home/me/.smbcredentials,dir_mode=0700,file_mode=0700 0 0 Any idea, why Nautilus is uploading up to 10 times more slowly than rsync, although both using the same cifs, os, hardware, network etc.? PS: Further info for bug report 1) The release of Ubuntu: Ubuntu 18.04 LTS 2) The version of the package: Nautilus 3.26.3 3) What you expected to happen: At least same speed as with using rsync 4) What happened instead: See above To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1782535/+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 1428356] Re: 03f0:2b17 USB HP LaserJet 1020 printer will not print after boot
Michael Baker, as this report is closed, it will help immensely if you filed a new report with Ubuntu via a terminal: ubuntu-bug cups Please feel free to subscribe me to it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1428356 Title: 03f0:2b17 USB HP LaserJet 1020 printer will not print after boot Status in HPLIP: Invalid Status in hplip package in Ubuntu: Invalid Bug description: After a reboot due to cups related package update my HP1020 printer is not initialized. This is shown in my syslog: Mar 4 15:32:42 localhost kernel: [ 178.196280] usblp 1-3.5:1.0: usblp0: USB Bidirectional printer dev 5 if 0 alt 0 proto 2 vid 0x03F0 pid 0x2B17 Mar 4 15:32:42 localhost kernel: [ 178.198667] usblp0: removed Mar 4 15:32:53 localhost kernel: [ 189.196356] usblp 1-3.5:1.0: usblp0: USB Bidirectional printer dev 5 if 0 alt 0 proto 2 vid 0x03F0 pid 0x2B17 Mar 4 15:32:53 localhost kernel: [ 189.198743] usblp0: removed Mar 4 15:33:04 localhost kernel: [ 200.196869] usblp 1-3.5:1.0: usblp0: USB Bidirectional printer dev 5 if 0 alt 0 proto 2 vid 0x03F0 pid 0x2B17 Mar 4 15:33:04 localhost kernel: [ 200.199629] usblp0: removed Mar 4 15:33:15 localhost kernel: [ 211.200586] usblp 1-3.5:1.0: usblp0: USB Bidirectional printer dev 5 if 0 alt 0 proto 2 vid 0x03F0 pid 0x2B17 This just continues on for hundreds of entries until I unplug and replug the printer back in, and power cycle several times. It will then eventually print a test page via 'CUPS'. Some other information from my syslog: Mar 4 15:42:10 localhost kernel: [ 746.297929] usblp: can't set desired altsetting 0 on interface 0 Mar 4 15:42:10 localhost kernel: [ 746.488804] usb 1-3.5: USB disconnect, device number 5 Mar 4 15:42:14 localhost kernel: [ 750.528166] usb 1-3.5: new high-speed USB device number 7 using ehci-pci Mar 4 15:42:16 localhost udev-configure-printer: remove /devices/pci:00/:00:1a.7/usb1/1-3/1-3.5 Mar 4 15:42:16 localhost colord: device removed: sysfs-Hewlett-Packard-HP_LaserJet_1020 Mar 4 15:42:23 localhost kernel: [ 758.976137] usb 1-3.5: new high-speed USB device number 8 using ehci-pci Mar 4 15:42:23 localhost kernel: [ 759.088384] usb 1-3.5: New USB device found, idVendor=03f0, idProduct=2b17 Mar 4 15:42:23 localhost kernel: [ 759.088389] usb 1-3.5: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Mar 4 15:42:23 localhost kernel: [ 759.088392] usb 1-3.5: Product: HP LaserJet 1020 Mar 4 15:42:23 localhost kernel: [ 759.088394] usb 1-3.5: Manufacturer: Hewlett-Packard Mar 4 15:42:23 localhost kernel: [ 759.088396] usb 1-3.5: SerialNumber: JL1F0DC Mar 4 15:42:23 localhost kernel: [ 759.091958] usblp 1-3.5:1.0: usblp0: USB Bidirectional printer dev 8 if 0 alt 0 proto 2 vid 0x03F0 pid 0x2B17 Mar 4 15:42:23 localhost logger: loading HP Device 001 008 Mar 4 15:42:23 localhost udev-configure-printer: add /devices/pci:00/:00:1a.7/usb1/1-3/1-3.5 Mar 4 15:42:23 localhost udev-configure-printer: device devpath is /devices/pci:00/:00:1a.7/usb1/1-3/1-3.5 Mar 4 15:42:23 localhost udev-configure-printer: MFG:Hewlett-Packard MDL:HP LaserJet 1020 SERN:- serial:JL1F0DC Mar 4 15:42:24 localhost kernel: [ 760.148568] usblp0: removed Mar 4 15:42:24 localhost kernel: [ 760.159830] usblp 1-3.5:1.0: usblp0: USB Bidirectional printer dev 8 if 0 alt 0 proto 2 vid 0x03F0 pid 0x2B17 Mar 4 15:42:24 localhost udev-configure-printer: URI contains USB serial number Mar 4 15:42:24 localhost udev-configure-printer: URI match: usb://HP/LaserJet%201020?serial=JL1F0DC Mar 4 15:42:24 localhost udev-configure-printer: SERN field matches USB serial number Mar 4 15:42:24 localhost udev-configure-printer: URI match: hp:/usb/HP_LaserJet_1020?serial=JL1F0DC Mar 4 15:42:24 localhost udev-configure-printer: URI of detected printer: usb://HP/LaserJet%201020?serial=JL1F0DC, normalized: laserjet 1020 serial jl1f0dc Mar 4 15:42:24 localhost udev-configure-printer: URI of print queue: usb://HP/LaserJet%201020?serial=JL1F0DC, normalized: laserjet 1020 serial jl1f0dc Mar 4 15:42:24 localhost udev-configure-printer: Queue ipp://localhost:631/printers/HP-LaserJet-1020 has matching device URI Mar 4 15:42:24 localhost udev-configure-printer: URI of detected printer: hp:/usb/HP_LaserJet_1020?serial=JL1F0DC, normalized: laserjet 1020 serial jl1f0dc Mar 4 15:42:24 localhost udev-configure-printer: Queue ipp://localhost:631/printers/HP-LaserJet-1020 has matching device URI Mar 4 15:42:26 localhost kernel: [ 762.327990] usblp0: removed Mar 4 15:42:30 localhost colord: Device added: sysfs-Hewlett-Packard-HP_LaserJet_1020 chris@localhost:~$ lsusb Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 008 Device 002: ID 046d:c31c Logitech, Inc. Keyboard K120 for Business
[Desktop-packages] [Bug 1833749] [NEW] unfocused terminal window blinking because of transparency unreasonably changing
Public bug reported: unfocused terminal window blinking because of transparency unreasonably changing without any action on keyboard nor mouse ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8 Uname: Linux 5.0.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 418.56 Fri Mar 15 12:59:26 CDT 2019 GCC version: gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1) ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 21 20:01:45 2019 DistUpgraded: 2019-04-19 17:34:11,213 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: disco DistroVariant: ubuntu DkmsStatus: nvidia, 418.56, 5.0.0-16-generic, x86_64: installed nvidia, 418.56, 5.0.0-17-generic, x86_64: installed virtualbox, 6.0.6, 5.0.0-16-generic, x86_64: installed virtualbox, 6.0.6, 5.0.0-17-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: NVIDIA Corporation GM107GLM [Quadro M2000M] [10de:13b0] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Lenovo GM107GLM [Quadro M2000M] [17aa:2230] InstallationDate: Installed on 2018-04-27 (420 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 20EN0008XS ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-17-generic root=UUID=9ba5bcf6-c098-48cd-b443-cbb9ab3b0f03 ro quiet splash acpi_sleep=nonvs vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to disco on 2019-04-19 (63 days ago) dmi.bios.date: 02/21/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1EET83W (1.56 ) dmi.board.asset.tag: Not Available dmi.board.name: 20EN0008XS dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1EET83W(1.56):bd02/21/2019:svnLENOVO:pn20EN0008XS:pvrThinkPadP50:rvnLENOVO:rn20EN0008XS:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P50 dmi.product.name: 20EN0008XS dmi.product.sku: LENOVO_MT_20EN_BU_Think_FM_ThinkPad P50 dmi.product.version: ThinkPad P50 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco third-party-packages ubuntu ** Attachment added: "terminal-transparency-unreasonably-changing" https://bugs.launchpad.net/bugs/1833749/+attachment/5272172/+files/terminal-transparency-unreasonably-changing.mp4 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1833749 Title: unfocused terminal window blinking because of transparency unreasonably changing Status in xorg package in Ubuntu: New Bug description: unfocused terminal window blinking because of transparency unreasonably changing without any action on keyboard nor mouse ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8 Uname: Linux 5.0.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 418.56 Fri Mar 15 12:59:26 CDT 2019 GCC version: gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1) ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 21 20:01:45 2019 DistUpgraded:
[Desktop-packages] [Bug 1832869] Re: gnome-shell crashed with SIGSEGV in g_hash_table_iter_next → meta_display_list_windows → meta_workspace_list_windows → ffi_call_SYSV → ffi_call()
I've done some more debugging on this, it happens mostly on Alt+f2 or shell restart, and seems to be due to dash-to-dock giu 21 19:44:08 tricky org.gnome.Shell.desktop[32227]: == Stack trace for context 0x55c4534674c0 == giu 21 19:44:08 tricky org.gnome.Shell.desktop[32227]: #0 0x55c4537ed038 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/theming.js:479 (0x7f71e459b560 @ 210) giu 21 19:44:08 tricky org.gnome.Shell.desktop[32227]: #1 0x7ffc64834670 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f72382b5de0 @ 71) giu 21 19:44:08 tricky org.gnome.Shell.desktop[32227]: #2 0x55c4537ecfa0 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/theming.js:451 (0x7f71e459b4d8 @ 23) giu 21 19:44:08 tricky org.gnome.Shell.desktop[32227]: #3 0x7ffc64835250 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f72382b5de0 @ 71) giu 21 19:44:08 tricky org.gnome.Shell.desktop[32227]: #4 0x55c4537ecf18 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/theming.js:447 (0x7f71e459b3c8 @ 117) giu 21 19:44:08 tricky org.gnome.Shell.desktop[32227]: #5 0x7ffc64835e40 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f72382b5de0 @ 71) giu 21 19:44:08 tricky org.gnome.Shell.desktop[32227]: #6 0x7ffc64835f10 b self-hosted:918 (0x7f72382f12b8 @ 394) giu 21 19:44:08 tricky org.gnome.Shell.desktop[32227]: #7 0x55c4537ecea0 i resource:///org/gnome/shell/ui/main.js:206 (0x7f72382da4d8 @ 12) ** Also affects: gnome-shell-extension-dashtodock (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-shell-extension-dashtodock (Ubuntu) Status: New => Triaged ** Changed in: gnome-shell-extension-dashtodock (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1832869 Title: gnome-shell crashed with SIGSEGV in g_hash_table_iter_next → meta_display_list_windows → meta_workspace_list_windows → ffi_call_SYSV → ffi_call() Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-dashtodock package in Ubuntu: Triaged Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.28.4-0ubuntu18.04.1, the problem page at https://errors.ubuntu.com/problem/d3f9725b7fae2763643521acfc58c734f829dd64 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. https://errors.ubuntu.com/problem/ac8df0b1e2d67e423c634fde1a3acecd3c381d58 https://errors.ubuntu.com/problem/d3f9725b7fae2763643521acfc58c734f829dd64 https://errors.ubuntu.com/problem/1e69eadeb69f4e2b8aa933205d2be3a8db4af36c https://errors.ubuntu.com/problem/6f7810166a3ae02cc8025514d6ffbbde10063e76 https://errors.ubuntu.com/problem/1bfbc00c70cfe6f4f2b66b4efc86f5c089c28680 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1832869/+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 1833745] [NEW] [MIR] required new dependency of appstream
Public bug reported: https://github.com/ximion/appstream/commit/358e9394631b87797f56dcb7e09e459b4044e631#commitcomment-33995178 Quote "Compiling AppStream without LMDB is not really possible." appstream/0.12.7-1 currently in -proposed now depends on liblmdb0 (>= 0.9.7) ** Affects: lmdb (Ubuntu) Importance: Undecided Status: New ** Description changed: https://github.com/ximion/appstream/commit/358e9394631b87797f56dcb7e09e459b4044e631#commitcomment-33995178 Quote "Compiling AppStream without LMDB is not really possible." - appstream/0.12.7-1 now depends on liblmdb0 (>= 0.9.7) + appstream/0.12.7-1 current in -proposed now depends on liblmdb0 (>= + 0.9.7) ** Description changed: https://github.com/ximion/appstream/commit/358e9394631b87797f56dcb7e09e459b4044e631#commitcomment-33995178 Quote "Compiling AppStream without LMDB is not really possible." - appstream/0.12.7-1 current in -proposed now depends on liblmdb0 (>= + appstream/0.12.7-1 currently in -proposed now depends on liblmdb0 (>= 0.9.7) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lmdb in Ubuntu. https://bugs.launchpad.net/bugs/1833745 Title: [MIR] required new dependency of appstream Status in lmdb package in Ubuntu: New Bug description: https://github.com/ximion/appstream/commit/358e9394631b87797f56dcb7e09e459b4044e631#commitcomment-33995178 Quote "Compiling AppStream without LMDB is not really possible." appstream/0.12.7-1 currently in -proposed now depends on liblmdb0 (>= 0.9.7) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lmdb/+bug/1833745/+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 1828884] Re: [META] Handling Japanese new era "令和 (Reiwa)"
On 2019-06-21 15:59, Mathieu Trudel-Lapierre wrote: > Looks like noto sources now have the right glyphs (since their April > 9 release, actually). Right. There are 2 months old merge requests in Debian to get them in: https://salsa.debian.org/fonts-team/fonts-noto-cjk/merge_requests But nobody has reacted to those requests yet AFAIK. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gucharmap in Ubuntu. https://bugs.launchpad.net/bugs/1828884 Title: [META] Handling Japanese new era "令和 (Reiwa)" Status in Poppler: New Status in fonts-noto-cjk package in Ubuntu: New Status in gucharmap package in Ubuntu: New Status in icu package in Ubuntu: New Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice-l10n package in Ubuntu: Fix Released Status in mozc package in Ubuntu: Fix Released Status in openjdk-8 package in Ubuntu: Fix Released Status in poppler-data package in Ubuntu: New Status in unicode-data package in Ubuntu: Fix Released Status in gnome-characters source package in Xenial: New Status in gucharmap source package in Xenial: New Status in icu source package in Xenial: New Status in libreoffice source package in Xenial: Fix Released Status in libreoffice-l10n source package in Xenial: Fix Released Status in mozc source package in Xenial: Fix Released Status in openjdk-8 source package in Xenial: New Status in poppler-data source package in Xenial: New Status in unicode-data source package in Xenial: New Status in fonts-noto-cjk source package in Bionic: New Status in gucharmap source package in Bionic: New Status in icu source package in Bionic: New Status in libreoffice source package in Bionic: Fix Released Status in libreoffice-l10n source package in Bionic: Fix Released Status in mozc source package in Bionic: Fix Released Status in openjdk-8 source package in Bionic: New Status in poppler-data source package in Bionic: New Status in unicode-data source package in Bionic: New Status in fonts-noto-cjk source package in Cosmic: New Status in gnome-characters source package in Cosmic: New Status in gucharmap source package in Cosmic: New Status in icu source package in Cosmic: New Status in libreoffice source package in Cosmic: Fix Released Status in libreoffice-l10n source package in Cosmic: Fix Released Status in mozc source package in Cosmic: Fix Released Status in openjdk-8 source package in Cosmic: New Status in poppler-data source package in Cosmic: New Status in unicode-data source package in Cosmic: New Status in fonts-noto-cjk source package in Disco: New Status in gnome-characters source package in Disco: New Status in gucharmap source package in Disco: New Status in icu source package in Disco: New Status in libreoffice source package in Disco: Fix Released Status in libreoffice-l10n source package in Disco: Fix Released Status in mozc source package in Disco: Fix Released Status in openjdk-8 source package in Disco: New Status in poppler-data source package in Disco: New Status in unicode-data source package in Disco: New Bug description: [Background] Many packages are affected by the requirement to support the new era "Reiwa" (令和） This is the meta bug to track packages that need fixes; which packages have already been SRUd to previous releases, how to prioritize the work needed, and general test cases for verifying that things are working as expected. [Impact] Users who run Ubuntu in Japanese. [Test cases] == Date conversion == On applications that support writing dates in long form, or with symbols to denote era (either in X00.00.00 format or in GG1G5G1G format (G- glyph; X- character): 1) Enable date formatting in each of the above formats that are supported (long form or symbols) 2) Type in '2019/05/01' to be formatted, verify that it shows as "令和1年5月1日" or "R1.05.01" 3) Type in '2019/04/30' to be formatted, verify that it shows as "平成31年4月30日" or "H31.4.30" == Date output == 1) Set date to 2019/05/01 2) Output date; verify that the year it is displayed as "令和元年" 3) Set date to 2019/04/30 4) Output date; verify that the year is diplayed as "平成31年" === Displaying formatted year for Japanese era with glibc === Run: LC_ALL=ja_JP.utf8 date +%EY -d 20190430 # previous era (should still work as before SRUs) or LC_ALL=ja_JP.utf8 date +%EY -d 20190501 # new era (should now correctly display the new era) == Character maps / font support == 1) Search for character "SQUARE ERA NAME" 2) Verify that the results include at least "SQUARE ERA NAME HEISEI" and "SQUARE ERA NAME REIWA" (there should also be Syouwa, Taisyou and Meizi), and that the glyphs are readable: - SQUARE ERA NAME HEISEI: ㍻ - SQUARE ERA NAME REIWA: 令和 (in a single glyph) Display of the Reiwa square glyph is font-specific; it may show simply as a empty
[Desktop-packages] [Bug 1428356] Re: 03f0:2b17 USB HP LaserJet 1020 printer will not print after boot
Just thought I'd share my miser with the HP 1020 printer. I've suddenly started having the same issues with my HP 1020. Running MATE 19.04, with mainline 5.1.9 kernel, and HPLIP 3.19.5 I've removed and install HPLIP from scratch (multiple times), printer works fine, but after reboot I get HPLIP pop up "printer communication error" messages, and when doing dmesg, i get "device descriptor read/64, error -110" regardless of which USB port I plug into. Just today, I used the hp-firmware command as recommended in this thread, and often times that fixes the issue, until i reboot or turn printer off. I should mention that I was NOT having any printer issues while i was using 18.04.2 LTS. All these issues surfaced after I moved to 19.04 (fresh install, not an upgrade). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1428356 Title: 03f0:2b17 USB HP LaserJet 1020 printer will not print after boot Status in HPLIP: Invalid Status in hplip package in Ubuntu: Invalid Bug description: After a reboot due to cups related package update my HP1020 printer is not initialized. This is shown in my syslog: Mar 4 15:32:42 localhost kernel: [ 178.196280] usblp 1-3.5:1.0: usblp0: USB Bidirectional printer dev 5 if 0 alt 0 proto 2 vid 0x03F0 pid 0x2B17 Mar 4 15:32:42 localhost kernel: [ 178.198667] usblp0: removed Mar 4 15:32:53 localhost kernel: [ 189.196356] usblp 1-3.5:1.0: usblp0: USB Bidirectional printer dev 5 if 0 alt 0 proto 2 vid 0x03F0 pid 0x2B17 Mar 4 15:32:53 localhost kernel: [ 189.198743] usblp0: removed Mar 4 15:33:04 localhost kernel: [ 200.196869] usblp 1-3.5:1.0: usblp0: USB Bidirectional printer dev 5 if 0 alt 0 proto 2 vid 0x03F0 pid 0x2B17 Mar 4 15:33:04 localhost kernel: [ 200.199629] usblp0: removed Mar 4 15:33:15 localhost kernel: [ 211.200586] usblp 1-3.5:1.0: usblp0: USB Bidirectional printer dev 5 if 0 alt 0 proto 2 vid 0x03F0 pid 0x2B17 This just continues on for hundreds of entries until I unplug and replug the printer back in, and power cycle several times. It will then eventually print a test page via 'CUPS'. Some other information from my syslog: Mar 4 15:42:10 localhost kernel: [ 746.297929] usblp: can't set desired altsetting 0 on interface 0 Mar 4 15:42:10 localhost kernel: [ 746.488804] usb 1-3.5: USB disconnect, device number 5 Mar 4 15:42:14 localhost kernel: [ 750.528166] usb 1-3.5: new high-speed USB device number 7 using ehci-pci Mar 4 15:42:16 localhost udev-configure-printer: remove /devices/pci:00/:00:1a.7/usb1/1-3/1-3.5 Mar 4 15:42:16 localhost colord: device removed: sysfs-Hewlett-Packard-HP_LaserJet_1020 Mar 4 15:42:23 localhost kernel: [ 758.976137] usb 1-3.5: new high-speed USB device number 8 using ehci-pci Mar 4 15:42:23 localhost kernel: [ 759.088384] usb 1-3.5: New USB device found, idVendor=03f0, idProduct=2b17 Mar 4 15:42:23 localhost kernel: [ 759.088389] usb 1-3.5: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Mar 4 15:42:23 localhost kernel: [ 759.088392] usb 1-3.5: Product: HP LaserJet 1020 Mar 4 15:42:23 localhost kernel: [ 759.088394] usb 1-3.5: Manufacturer: Hewlett-Packard Mar 4 15:42:23 localhost kernel: [ 759.088396] usb 1-3.5: SerialNumber: JL1F0DC Mar 4 15:42:23 localhost kernel: [ 759.091958] usblp 1-3.5:1.0: usblp0: USB Bidirectional printer dev 8 if 0 alt 0 proto 2 vid 0x03F0 pid 0x2B17 Mar 4 15:42:23 localhost logger: loading HP Device 001 008 Mar 4 15:42:23 localhost udev-configure-printer: add /devices/pci:00/:00:1a.7/usb1/1-3/1-3.5 Mar 4 15:42:23 localhost udev-configure-printer: device devpath is /devices/pci:00/:00:1a.7/usb1/1-3/1-3.5 Mar 4 15:42:23 localhost udev-configure-printer: MFG:Hewlett-Packard MDL:HP LaserJet 1020 SERN:- serial:JL1F0DC Mar 4 15:42:24 localhost kernel: [ 760.148568] usblp0: removed Mar 4 15:42:24 localhost kernel: [ 760.159830] usblp 1-3.5:1.0: usblp0: USB Bidirectional printer dev 8 if 0 alt 0 proto 2 vid 0x03F0 pid 0x2B17 Mar 4 15:42:24 localhost udev-configure-printer: URI contains USB serial number Mar 4 15:42:24 localhost udev-configure-printer: URI match: usb://HP/LaserJet%201020?serial=JL1F0DC Mar 4 15:42:24 localhost udev-configure-printer: SERN field matches USB serial number Mar 4 15:42:24 localhost udev-configure-printer: URI match: hp:/usb/HP_LaserJet_1020?serial=JL1F0DC Mar 4 15:42:24 localhost udev-configure-printer: URI of detected printer: usb://HP/LaserJet%201020?serial=JL1F0DC, normalized: laserjet 1020 serial jl1f0dc Mar 4 15:42:24 localhost udev-configure-printer: URI of print queue: usb://HP/LaserJet%201020?serial=JL1F0DC, normalized: laserjet 1020 serial jl1f0dc Mar 4 15:42:24 localhost udev-configure-printer: Queue ipp://localhost:631/printers/HP-LaserJet-1020 has matching device URI Mar 4
[Desktop-packages] [Bug 1630137] Re: gstreamer1.0-vaapi depends on libgstreamer-plugins-bad1.0-0 (<< 1.8.1) but 1.8.2 is in the archive
Could either of you please run `sudo apt update` and attach the output from `apt show gstreamer1.0-vaapi` afterwards? It is hard to tell, but based on the screenshot it seems to consider an older version of gstreamer1.0-vaapi as the latest which cause problems when the dependencies find the newer versions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1630137 Title: gstreamer1.0-vaapi depends on libgstreamer-plugins-bad1.0-0 (<< 1.8.1) but 1.8.2 is in the archive Status in gstreamer1.0 package in Ubuntu: Expired Bug description: gstreamer1.0-vaapi depends on libgstreamer-plugins-bad1.0-0 (<< 1.8.1) but 1.8.2 is in the archive, so the consequence is that nobody can install package `gstreamer1.0-vaapi` now: $ sudo apt install gstreamer1.0-vaapi Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: gstreamer1.0-vaapi : Depends: libgstreamer-plugins-bad1.0-0 (< 1.8.1) but 1.8.2-1ubuntu0.1 is to be installed E: Unable to correct problems, you have held broken packages. Tested in recently installed Ubuntu 16.04.1. The culprit seems to be in: $ apt-cache show gstreamer1.0-vaapi Package: gstreamer1.0-vaapi Priority: optional Section: universe/libs Installed-Size: 714 Maintainer: Ubuntu Developers Original-Maintainer: Maintainers of GStreamer packages Architecture: amd64 Source: gstreamer-vaapi Version: 1.8.0-1 Depends: libc6 (>= 2.14), libdrm2 (>= 2.3.1), libegl1-mesa (>= 7.8.1) | libegl1-x11, libgl1-mesa-glx | libgl1, libglib2.0-0 (>= 2.37.3), libgstreamer-plugins-bad1.0-0 (>= 1.8.0), libgstreamer-plugins-bad1.0-0 (<< 1.8.1), libgstreamer-plugins-base1.0-0 (>= 1.6.0), libgstreamer1.0-0 (>= 1.6.0), libudev1 (>= 183), libva-drm1 (>= 1.1.0), libva-wayland1 (>= 1.3.0), libva-x11-1 (>= 1.0.3), libva1 (>= 1.4.0), libwayland-client0 (>= 1.3.92), libx11-6, libxrandr2, libxrender1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1630137/+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 1630137] Re: gstreamer1.0-vaapi depends on libgstreamer-plugins-bad1.0-0 (<< 1.8.1) but 1.8.2 is in the archive
...oh, and the output from `apt policy gstreamer1.0-vaapi` as well? :) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1630137 Title: gstreamer1.0-vaapi depends on libgstreamer-plugins-bad1.0-0 (<< 1.8.1) but 1.8.2 is in the archive Status in gstreamer1.0 package in Ubuntu: Expired Bug description: gstreamer1.0-vaapi depends on libgstreamer-plugins-bad1.0-0 (<< 1.8.1) but 1.8.2 is in the archive, so the consequence is that nobody can install package `gstreamer1.0-vaapi` now: $ sudo apt install gstreamer1.0-vaapi Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: gstreamer1.0-vaapi : Depends: libgstreamer-plugins-bad1.0-0 (< 1.8.1) but 1.8.2-1ubuntu0.1 is to be installed E: Unable to correct problems, you have held broken packages. Tested in recently installed Ubuntu 16.04.1. The culprit seems to be in: $ apt-cache show gstreamer1.0-vaapi Package: gstreamer1.0-vaapi Priority: optional Section: universe/libs Installed-Size: 714 Maintainer: Ubuntu Developers Original-Maintainer: Maintainers of GStreamer packages Architecture: amd64 Source: gstreamer-vaapi Version: 1.8.0-1 Depends: libc6 (>= 2.14), libdrm2 (>= 2.3.1), libegl1-mesa (>= 7.8.1) | libegl1-x11, libgl1-mesa-glx | libgl1, libglib2.0-0 (>= 2.37.3), libgstreamer-plugins-bad1.0-0 (>= 1.8.0), libgstreamer-plugins-bad1.0-0 (<< 1.8.1), libgstreamer-plugins-base1.0-0 (>= 1.6.0), libgstreamer1.0-0 (>= 1.6.0), libudev1 (>= 183), libva-drm1 (>= 1.1.0), libva-wayland1 (>= 1.3.0), libva-x11-1 (>= 1.0.3), libva1 (>= 1.4.0), libwayland-client0 (>= 1.3.92), libx11-6, libxrandr2, libxrender1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1630137/+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 1832442] Re: Evince Not printing Font
** Changed in: evince (Ubuntu) Importance: Undecided => Low ** Changed in: evince (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1832442 Title: Evince Not printing Font Status in Evince: New Status in evince package in Ubuntu: Triaged Bug description: The attached pdf file only prints the lines of the form all text are missing. I also attached a scan of how the printout looks. The problem do not show at first start, some factor during the day is the starting point then from that point only a restart fix the problem. I have a work around at this stage. I change the font from Arial to Times New Roman. As of yet I didn't have the problem on Times New Roman. The Windows fonts is installed on the Ubuntu. Document was created on Google Sheets. The print process created the pdf. If I print the document via Firefox it prints correct. System Info Ubuntu 18.04 Fully patched Evince 3.28.4 hplip 3.19.5 (Upgraded the Ubuntu hplip to newest version to see if that was problem it didn't help) printer: HP LaserJet Pro M201n Evince Ticket Link: https://gitlab.gnome.org/GNOME/evince/issues/1165 To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/1832442/+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 1825710] Re: Remove "Application is ready" notification
** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1825710 Title: Remove "Application is ready" notification Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Triaged Bug description: The "Application is ready" notification is pointless, really. Say, I click on the open downloads folder button in Firefox and GNOME Shell gives me a notification saying "Application is ready" but doesn't open the notification. I'm totally expecting an app to open because I actively initiated it. As a workaround, I'm using a GNOME extensions "Focus my Window" which removes the "Application is ready" message and focuses the app window automatically. However, this cannot be treated as a solution. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1825710/+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 1832695] Re: gedit -w -s crashes with SIGSEGV
Thank you for your bug report, those options indeed seem incompatible, that should be reported upstream on https://gitlab.gnome.org/GNOME/gedit/issues/ ** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1832695 Title: gedit -w -s crashes with SIGSEGV Status in gedit package in Ubuntu: New Bug description: After doing a git config --global core.editor "gedit -w -s" gedit crashes as soon as I try to commit something using git. git config --global core.editor "gedit -s" works fine, though => Something is wrong with gedit's '-w' switch. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: gedit 3.32.0-3 ProcVersionSignature: Ubuntu 5.0.0-16.17-lowlatency 5.0.8 Uname: Linux 5.0.0-16-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jun 13 11:14:26 2019 ExecutablePath: /usr/bin/gedit InstallationDate: Installed on 2019-05-26 (18 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcCmdline: gedit -w -s /home/username/src/maxima-code/.git/COMMIT_EDITMSG SegvAnalysis: Segfault happened at: 0x7fb5d8619518:mov0x30(%rdi),%eax PC (0x7fb5d8619518) ok source "0x30(%rdi)" (0x0030) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gedit StacktraceTop: () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 g_application_register () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 g_application_run () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: gedit crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare scanner sudo wireshark separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1832695/+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 1832693] Re: System auto suspend again during resuming
Thank you for your bug report, what Ubuntu version and desktop environment do you use? Could you add your journalctl log after triggering the issue? ** Changed in: gnome-settings-daemon (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-settings-daemon (Ubuntu) Status: New => Incomplete -- 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/1832693 Title: System auto suspend again during resuming Status in gnome-settings-daemon package in Ubuntu: Incomplete Bug description: ## Issue In certain case, system wake-up from suspend will suspend again automatically. The issue comes from a target machine turning auto-suspend on and suspends after the idle time-out. Manually suspend, e.g., click suspend icon or execute "systemctl suspend" won't reproduce the issue. When waking up from this situation, the monitor keeps blank, although the monitor has exited low power mode, then suspend again immediately. Can successfully waking up the system after that, but once the system reaches the idle time again, the issue appears repeatedly. From the system log, a sleep request is following the wake request. Hardware configuration also counts. It is hard to reproduce the issue with the system installed on SSD or with a lower resolution monitor; graphics card may also affect. It's likely to be a timing issue. ## Environment Machine: Dell Precision 7920 Tower. Monitor: Philips 288P6L DistroRelease: Ubuntu 18.04.2 Graphics card: Nvidia Quadro P2200 Nvidia driver version: 418.74 CPU: Intel(R) Xeon(R) Platinum 8276 CPU @ 2.20GHz ## Steps to reproduce: Turn on automatic suspend in Settings->Power Wait for the system to suspend Wake up the system via pressing power button or keyboard. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1832693/+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 1832414] Re: Removing document files spam from cups
Dariusz, Till, could you have a look? That's reported as a potential regression from the xenial SRU ** Changed in: cups (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1832414 Title: Removing document files spam from cups Status in cups package in Ubuntu: New Bug description: Since my server (running xenial) updated to cups 2.1.3-4ubuntu0.9 last night the CUPS logs have had a considerable number of messages from cupsd stating "Removing document files" - about 3 or 4 a second constantly. Stopping the cups service stops the log-spam, and starting it again immediately resumes it (after a few hundred "Loading from cache..." messages). I've tried removing document files from the cache (there were a couple of ancient ones lying around - it's not a heavily used printer), but this made little difference to the symptoms. I'm pretty confident this is due to the upgrade as: 1. the spam in the logs starts immediately after CUPS reloads (after the upgrade) 2. looking at the diff for 2.1.3-4ubuntu0.9 it does seem to be fiddling with things related to job clean-up (e.g. cupsdUpdateJobs and cupsdCleanJobs in scheduler/job.c) If I can provide any further information, do let me know! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1832414/+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 1782535] Re: cifs - poor upload speed with nautilus compared to rsync
Would still be good to backport to the LTS if we know what changed resolved the issue ** Changed in: glib2.0 (Ubuntu) Status: Triaged => Fix Released ** Bug watch added: gitlab.gnome.org/GNOME/glib/issues #1688 https://gitlab.gnome.org/GNOME/glib/issues/1688 ** Also affects: glib via https://gitlab.gnome.org/GNOME/glib/issues/1688 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1782535 Title: cifs - poor upload speed with nautilus compared to rsync Status in GLib: Unknown Status in glib2.0 package in Ubuntu: Fix Released Bug description: I'm mounting folders from my NAS on my computer (Ubuntu 18.04) with cifs. Copying an 8 GB file... Upload (local -> mounted) - Nautilus/Nemo -> 6 MB/s - rsync -> 50-60 MB/s Download performance is also strange, but not my biggest concern. Download (mounted -> local) - Nautilus/Nemo -> 90 MB/s - rsync -> 50-60 MB/s rsync command (upload): rsync --progress /home/me/file.iso /mnt/cifs_media/ fstab entry: //nas/media /mnt/cifs_media cifs vers=3.0,uid=me,gid=me,credentials=/home/me/.smbcredentials,dir_mode=0700,file_mode=0700 0 0 Any idea, why Nautilus is uploading up to 10 times more slowly than rsync, although both using the same cifs, os, hardware, network etc.? PS: Further info for bug report 1) The release of Ubuntu: Ubuntu 18.04 LTS 2) The version of the package: Nautilus 3.26.3 3) What you expected to happen: At least same speed as with using rsync 4) What happened instead: See above To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1782535/+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 1798961] Re: Random unrecoverable freezes on Ubuntu 18.10
@karl-piccket try booting with ahci.mobile_lpm_policy=0, and then try comment #42 if it doesn't work. -- 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/1798961 Title: Random unrecoverable freezes on Ubuntu 18.10 Status in Linux: New Status in linux package in Ubuntu: Triaged Status in xserver-xorg-video-intel package in Ubuntu: Invalid Status in linux source package in Bionic: Triaged Status in xserver-xorg-video-intel source package in Bionic: Invalid Status in linux source package in Cosmic: Triaged Status in xserver-xorg-video-intel source package in Cosmic: Invalid Status in linux source package in Disco: Triaged Status in xserver-xorg-video-intel source package in Disco: Invalid Bug description: First thing I notice is that the mouse cursor freezes as I'm using it, then I hit the CAPS LOCK key and the LED indicator doesn't respond. Then I try the "REISUB" command, but it doesn't do anything either. Only a hard reset works, pressing down the power button for a few seconds. How to reproduce? I couldn't figure out a consistent method. It is still random to me. Version: Ubuntu 4.18.0-10.11-generic 4.18.12 System information attached. Also happens under Arch Linux and Fedora. I've talked to another user on IRC who seems to be having the same freezes. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dsilva 1213 F pulseaudio /dev/snd/controlC0: dsilva 1213 F pulseaudio CurrentDesktop: XFCE Date: Sat Oct 20 09:54:50 2018 InstallationDate: Installed on 2018-10-20 (0 days ago) InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: Dell Inc. Inspiron 5458 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/02/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 09WGNT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd02/02/2018:svnDellInc.:pnInspiron5458:pvr01:rvnDellInc.:rn09WGNT:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 5458 dmi.product.sku: Inspiron 5458 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1798961/+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 1832787] Re: fontconfig 2.12 in 18.04 causes firefox to freeze when launching chrome
Thank you for your bug report. The issue seems similar to https://bugzilla.mozilla.org/show_bug.cgi?id=1495900 ** Bug watch added: Mozilla Bugzilla #1495900 https://bugzilla.mozilla.org/show_bug.cgi?id=1495900 ** Changed in: fontconfig (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1832787 Title: fontconfig 2.12 in 18.04 causes firefox to freeze when launching chrome Status in fontconfig package in Ubuntu: New Bug description: fontconfig version: 2.12.6-0ubuntu2 Related: https://askubuntu.com/questions/1076412/firefox-freezing-with-100-cpu- usage-for-30-seconds-when-launching-chromium https://bugzilla.mozilla.org/show_bug.cgi?id=1495900 https://bugzilla.mozilla.org/show_bug.cgi?id=1411338 Steps to reproduce: 1) Launch firefox, open a few tabs 2) Launch chrome 3) Go back to firefox, and notice it starts being very slow, switching tabs do nothing (the content area remains blank). 4) Backport fontconfig 2.13 from cosmic to bionic 5) Try to reproduce 1-3, be happy because it is now working fine! I backported 2.13.0-5ubuntu3 from cosmic to bionic, if that helps. I don't have the right setup right now to do a bisect from upstream or from debian patches sadly. ~ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.2 LTS Release: 18.04 Codename: bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1832787/+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 1832426] Re: "Program" is not responding when debugging in gdb
Bug #1740869 was another issue and about the fact that the dialog would lead input to stop working, the bug here is about the fact that those dialogs are an annoyance and should be avoided for debuggers ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => High ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1832426 Title: "Program" is not responding when debugging in gdb Status in gnome-shell package in Ubuntu: Confirmed Bug description: I believe this is a regression for bug 1740869: is not responding window is constantly showing when debugging a program I'm debugging my c++ sdl2 program in gdb and when I hit a breakpoint this window shows up and I can't get it to stop asking me to close the program. 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Description: Ubuntu 19.04 Release: 19.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center gnome-shell: Installed: 3.32.1-1ubuntu1~19.04.1 Candidate: 3.32.1-1ubuntu1~19.04.1 Version table: *** 3.32.1-1ubuntu1~19.04.1 500 500 http://us.archive.ubuntu.com/ubuntu disco-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.32.0+git20190410-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages 3) What you expected to happen When I hit a breakpoint in gdb, the program should stop. 4) What happened instead The program stops and ubuntu asks me if i want to kill the program. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.1-1ubuntu1~19.04.1 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jun 11 22:03:44 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-06-08 (4 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1832426/+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
Re: [Desktop-packages] [Bug 1833617] Re: screen freeze after suspend
screen freeze results. Please let me know the cause thanks Daniel M. Levi On Thursday, June 20, 2019, 8:35:33 PM PDT, Daniel van Vugt wrote: Please reproduce the freeze again, then reboot and run: journalctl -b-1 > prevboot.txt and send us the file 'prevboot.txt'. ** Tags added: amdgpu ** Summary changed: - screen freeze after suspend + [amdgpu] screen freeze after suspend ** Package changed: xorg (Ubuntu) => xserver-xorg-video-amdgpu (Ubuntu) ** Changed in: xserver-xorg-video-amdgpu (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1833617 Title: [amdgpu] screen freeze after suspend Status in xserver-xorg-video-amdgpu package in Ubuntu: Incomplete Bug description: It's most likely amdgup driver needs an upgrade. Problem occurs since kernel upgrade to 5.0 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-18.19-generic 5.0.12 Uname: Linux 5.0.0-18-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CompositorRunning: None Date: Thu Jun 20 13:46:46 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] [1002:98e4] (rev eb) (prog-if 00 [VGA controller]) Subsystem: Dell Stoney [Radeon R2/R3/R4/R5 Graphics] [1028:087e] InstallationDate: Installed on 2019-06-06 (14 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. Inspiron 3180 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-18-generic root=UUID=a16bd163-e82f-4ec1-9c5f-c9bd32e225fa ro SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/09/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 0918N8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.3.0 dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd03/09/2018:svnDellInc.:pnInspiron3180:pvr1.3.0:rvnDellInc.:rn0918N8:rvrA00:cvnDellInc.:ct10:cvr1.3.0: dmi.product.family: Inspiron dmi.product.name: Inspiron 3180 dmi.product.sku: 087E dmi.product.version: 1.3.0 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1833617/+subscriptions ** Attachment added: "prevboot.txt" https://bugs.launchpad.net/bugs/1833617/+attachment/5272130/+files/prevboot.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1833617 Title: [amdgpu] screen freeze after suspend Status in xserver-xorg-video-amdgpu package in Ubuntu: Incomplete Bug description: It's most likely amdgup driver needs an upgrade. Problem occurs since kernel upgrade to 5.0 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-18.19-generic 5.0.12 Uname: Linux 5.0.0-18-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CompositorRunning: None Date: Thu Jun 20 13:46:46 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] [1002:98e4] (rev eb) (prog-if 00 [VGA controller]) Subsystem: Dell Stoney [Radeon R2/R3/R4/R5 Graphics] [1028:087e] InstallationDate: Installed on 2019-06-06 (14 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. Inspiron 3180 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-18-generic root=UUID=a16bd163-e82f-4ec1-9c5f-c9bd32e225fa ro SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/09/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 0918N8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.3.0 dmi.modalias:
[Desktop-packages] [Bug 1822515] Re: Touchscreen input doesn't rotate with the screen
The commit is in 3.32.2, needs to be SRUed to disco ** Changed in: xorg-server (Ubuntu) Status: Confirmed => Invalid ** Changed in: mutter (Ubuntu) Importance: Undecided => High ** Changed in: mutter (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1822515 Title: Touchscreen input doesn't rotate with the screen Status in mutter package in Ubuntu: Fix Committed Status in xorg-server package in Ubuntu: Invalid Bug description: When a touch screen is rotated, touch input is not mapped correctly. I'm testing 19.04 on an Acer-One S1003 where the default orientation is portrait. Ubuntu 19.04 support automatic screen rotation out of the box. But, when the tablet is in landscape, the touchscreen doesn't behave correctly. Moving a finger horizontally cause a vertical movement and vice versa. The same happens in both X11 and Wayland. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 Package: xorg-server PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Tags: disco Uname: Linux 5.0.0-13-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/mutter/+bug/1822515/+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 1833197] Re: crashes when creating annotations (Segmentation fault (core dumped))
Thank you for your bug report, what version of Ubuntu and evince are you using? Do you get a crash report in /var/crash? Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem. ** Changed in: evince (Ubuntu) Importance: Undecided => High ** Changed in: evince (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1833197 Title: crashes when creating annotations (Segmentation fault (core dumped)) Status in evince package in Ubuntu: Incomplete Bug description: After creating several annotations in a PDF document evince ends up crashing with an inespecific segfault terminal output. It happens always, but it takes a long time, so it's hard to reproduce, and it doesn't always happens in the same place, despite I've tried to hit the bug reopening and inserting an annotation in the same place. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1833197/+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 1833231] Re: cups ftbfs in eoan (amd64 only)
Till, can you have a look to this one? ** Changed in: cups (Ubuntu) Importance: Undecided => High ** Changed in: cups (Ubuntu) Assignee: (unassigned) => Till Kamppeter (till-kamppeter) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1833231 Title: cups ftbfs in eoan (amd64 only) Status in cups package in Ubuntu: New Bug description: cups ftbfs in eoan (amd64 only) in a test rebuild: https://launchpadlibrarian.net/428250411/buildlog_ubuntu-eoan- amd64.cups_2.2.10-6ubuntu1_BUILDING.txt.gz E [14/Jun/2019:14:46:57.037970 +] Unknown default SystemGroup "lpadmin". PASS: 8 warning messages. PASS: 0 notice messages. PASS: 760 info messages. PASS: 24065 debug messages. PASS: 25573 debug2 messages. Copied log file "access_log-2019-06-14-buildd" to test directory. Copied log file "debug_log-2019-06-14-buildd" to test directory. Copied log file "error_log-2019-06-14-buildd" to test directory. Copied log file "page_log-2019-06-14-buildd" to test directory. Copied report file "cups-str-2019-06-14-buildd.html" to test directory. 1 tests failed. make[2]: *** [Makefile:257: check] Error 1 make[2]: Leaving directory '/<>' make[1]: *** [debian/rules:201: override_dh_auto_test] Error 2 make[1]: Leaving directory '/<>' make: *** [debian/rules:17: build] Error 2 dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1833231/+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 1798961] Re: Random unrecoverable freezes on Ubuntu 18.10
I am using 19.04. I have a Pentium G4600 desktop (Intel NUC, kaby lake, intel 630 HD graphics) and have gotten hard lockups on average every 24 hours, and always while playing video usually in chrome. This system was rock solid with 18.04 :( -- 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/1798961 Title: Random unrecoverable freezes on Ubuntu 18.10 Status in Linux: New Status in linux package in Ubuntu: Triaged Status in xserver-xorg-video-intel package in Ubuntu: Invalid Status in linux source package in Bionic: Triaged Status in xserver-xorg-video-intel source package in Bionic: Invalid Status in linux source package in Cosmic: Triaged Status in xserver-xorg-video-intel source package in Cosmic: Invalid Status in linux source package in Disco: Triaged Status in xserver-xorg-video-intel source package in Disco: Invalid Bug description: First thing I notice is that the mouse cursor freezes as I'm using it, then I hit the CAPS LOCK key and the LED indicator doesn't respond. Then I try the "REISUB" command, but it doesn't do anything either. Only a hard reset works, pressing down the power button for a few seconds. How to reproduce? I couldn't figure out a consistent method. It is still random to me. Version: Ubuntu 4.18.0-10.11-generic 4.18.12 System information attached. Also happens under Arch Linux and Fedora. I've talked to another user on IRC who seems to be having the same freezes. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dsilva 1213 F pulseaudio /dev/snd/controlC0: dsilva 1213 F pulseaudio CurrentDesktop: XFCE Date: Sat Oct 20 09:54:50 2018 InstallationDate: Installed on 2018-10-20 (0 days ago) InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: Dell Inc. Inspiron 5458 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/02/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 09WGNT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd02/02/2018:svnDellInc.:pnInspiron5458:pvr01:rvnDellInc.:rn09WGNT:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 5458 dmi.product.sku: Inspiron 5458 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1798961/+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 1765902] Re: switch off the vpn ppt stop the wifi
*** This bug is a duplicate of bug 1778946 *** https://bugs.launchpad.net/bugs/1778946 Thanks! ** This bug has been marked a duplicate of bug 1778946 No dns resolution after closing a vpn/pptp connection -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-pptp in Ubuntu. https://bugs.launchpad.net/bugs/1765902 Title: switch off the vpn ppt stop the wifi Status in network-manager-pptp package in Ubuntu: Incomplete Bug description: On a gnome session After being connected by the pptp with a wifi connection, if I switch off the vpn then the wifi does not work anymore. I have to turn off the wifi and connect again for it to work ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager-pptp 1.2.6-1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 CurrentDesktop: communitheme:ubuntu:GNOME Date: Sat Apr 21 06:52:52 2018 InstallationDate: Installed on 2018-04-20 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180420) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: network-manager-pptp UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-pptp/+bug/1765902/+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 1833470] Re: ca0132 audio in Ubuntu 19.04 only after Windows 10 started
** Package changed: alsa-driver (Ubuntu) => linux (Ubuntu) -- 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/1833470 Title: ca0132 audio in Ubuntu 19.04 only after Windows 10 started Status in linux package in Ubuntu: Incomplete Bug description: Motherboard: Gigabyte GA-Z170X-Gaming GT (rev. 1.0) Description: Ubuntu 19.04 Release: 19.04 Expected behavior: Audio playback via headphones Actual behavior: No audio playback heard If I start Ubuntu 19.04 directly after booting my PC, there is no sound from the front or rear outputs. Everything seems configured correctly in Alsamixer, etc. If I boot into Windows 10, then restart and enter Ubuntu, the sound works as expected. I suspect something is being set properly by the Windows driver that is missed in the native Linux driver. The fact that it survives a (soft) reboot is interesting. I know this is at the ALSA level or below, because if I stop pulseaudio, `aplay music.wav` produces no output before starting Windows, and works after starting Windows. output of `lspci | grep -i audio` 00:1f.3 Audio device: Intel Corporation 100 Series/C230 Series Chipset Family HD Audio Controller (rev 31) 02:00.1 Audio device: NVIDIA Corporation GP104 High Definition Audio Controller (rev a1) output of `aplay -lL` default Playback/recording through the PulseAudio sound server null Discard all samples (playback) or generate zero samples (capture) jack JACK Audio Connection Kit pulse PulseAudio Sound Server sysdefault:CARD=PCH HDA Intel PCH, CA0132 Analog Default Audio Device front:CARD=PCH,DEV=0 HDA Intel PCH, CA0132 Analog Front speakers surround21:CARD=PCH,DEV=0 HDA Intel PCH, CA0132 Analog 2.1 Surround output to Front and Subwoofer speakers surround40:CARD=PCH,DEV=0 HDA Intel PCH, CA0132 Analog 4.0 Surround output to Front and Rear speakers surround41:CARD=PCH,DEV=0 HDA Intel PCH, CA0132 Analog 4.1 Surround output to Front, Rear and Subwoofer speakers surround50:CARD=PCH,DEV=0 HDA Intel PCH, CA0132 Analog 5.0 Surround output to Front, Center and Rear speakers surround51:CARD=PCH,DEV=0 HDA Intel PCH, CA0132 Analog 5.1 Surround output to Front, Center, Rear and Subwoofer speakers surround71:CARD=PCH,DEV=0 HDA Intel PCH, CA0132 Analog 7.1 Surround output to Front, Center, Side, Rear and Woofer speakers iec958:CARD=PCH,DEV=0 HDA Intel PCH, CA0132 Digital IEC958 (S/PDIF) Digital Audio Output dmix:CARD=PCH,DEV=0 HDA Intel PCH, CA0132 Analog Direct sample mixing device dmix:CARD=PCH,DEV=1 HDA Intel PCH, CA0132 Digital Direct sample mixing device dsnoop:CARD=PCH,DEV=0 HDA Intel PCH, CA0132 Analog Direct sample snooping device dsnoop:CARD=PCH,DEV=1 HDA Intel PCH, CA0132 Digital Direct sample snooping device hw:CARD=PCH,DEV=0 HDA Intel PCH, CA0132 Analog Direct hardware device without any conversions hw:CARD=PCH,DEV=1 HDA Intel PCH, CA0132 Digital Direct hardware device without any conversions plughw:CARD=PCH,DEV=0 HDA Intel PCH, CA0132 Analog Hardware device with all software conversions plughw:CARD=PCH,DEV=1 HDA Intel PCH, CA0132 Digital Hardware device with all software conversions usbstream:CARD=PCH HDA Intel PCH USB Stream Output hdmi:CARD=NVidia,DEV=0 HDA NVidia, HDMI 0 HDMI Audio Output hdmi:CARD=NVidia,DEV=1 HDA NVidia, HDMI 1 HDMI Audio Output hdmi:CARD=NVidia,DEV=2 HDA NVidia, HDMI 2 HDMI Audio Output hdmi:CARD=NVidia,DEV=3 HDA NVidia, HDMI 3 HDMI Audio Output dmix:CARD=NVidia,DEV=3 HDA NVidia, HDMI 0 Direct sample mixing device dmix:CARD=NVidia,DEV=7 HDA NVidia, HDMI 1 Direct sample mixing device dmix:CARD=NVidia,DEV=8 HDA NVidia, HDMI 2 Direct sample mixing device dmix:CARD=NVidia,DEV=9 HDA NVidia, HDMI 3 Direct sample mixing device dsnoop:CARD=NVidia,DEV=3 HDA NVidia, HDMI 0 Direct sample snooping device dsnoop:CARD=NVidia,DEV=7 HDA NVidia, HDMI 1 Direct sample snooping device dsnoop:CARD=NVidia,DEV=8 HDA NVidia, HDMI 2 Direct sample snooping device dsnoop:CARD=NVidia,DEV=9 HDA NVidia, HDMI 3 Direct sample snooping device hw:CARD=NVidia,DEV=3 HDA NVidia, HDMI 0 Direct hardware device without any conversions hw:CARD=NVidia,DEV=7 HDA NVidia, HDMI 1 Direct hardware device without any conversions hw:CARD=NVidia,DEV=8 HDA NVidia, HDMI 2 Direct hardware device without any conversions hw:CARD=NVidia,DEV=9 HDA NVidia, HDMI 3 Direct hardware device without any conversions plughw:CARD=NVidia,DEV=3 HDA NVidia,
[Desktop-packages] [Bug 1833440] Re: My University disabled NTLMv1 and Evolution won't let me authenticate to Exchange
*** This bug is a duplicate of bug 1817537 *** https://bugs.launchpad.net/bugs/1817537 ** This bug has been marked a duplicate of bug 1817537 libsoup should support ntlmv2 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libsoup2.4 in Ubuntu. https://bugs.launchpad.net/bugs/1833440 Title: My University disabled NTLMv1 and Evolution won't let me authenticate to Exchange Status in libsoup2.4 package in Ubuntu: New Bug description: There is a newer version of libsoup that allows NTLMv2 authentication that resolves this issue. Here is a bug from the Gnome libsoup bug report: https://gitlab.gnome.org/GNOME/libsoup/issues/114 In this bug report for Evolution: https://gitlab.gnome.org/GNOME/evolution-ews/issues/38 someone mentions "the change landed after 2.64.0 and before 2.65.1 and seems to be part of 2.65.1+ only" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsoup2.4/+bug/1833440/+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 1833508] Re: the system woke up and has not proper desktop image
Thank you for your bug report, could you run that command $ apport-collect 1833508 What video card/driver are you using? Could you add your journalctl log to the bug after getting the issue? ** Package changed: systemd (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1833508 Title: the system woke up and has not proper desktop image Status in gnome-shell package in Ubuntu: Incomplete Bug description: i have ubuntu 19.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1833508/+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 1833508] [NEW] the system woke up and has not proper desktop image
You have been subscribed to a public bug: i have ubuntu 19.04 ** Affects: gnome-shell (Ubuntu) Importance: Low Status: Incomplete -- the system woke up and has not proper desktop image https://bugs.launchpad.net/bugs/1833508 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. -- 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 1833512] Re: Wifi password dialog popup don't take more the 20 ASCII-encoded characters
Thank you for your bug report. Could you take a screenshot of the dialog you are talking about? How do you try to connect? What happens when you type more than 20 chars? ** Changed in: network-manager (Ubuntu) Importance: Undecided => Low ** Changed in: network-manager (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1833512 Title: Wifi password dialog popup don't take more the 20 ASCII-encoded characters Status in network-manager package in Ubuntu: Incomplete Bug description: The max pass-phrase length for a WPA2-PSK, has a limit of 63 ASCII- encoded characters The password fields, in the dialog to write the pass-phrase for the Wifi network you are connecting to, is limiting this to 20 characters. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: network-manager 1.16.0-0ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8 Uname: Linux 5.0.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jun 20 09:59:57 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2019-06-19 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) IpRoute: default via 192.168.1.1 dev enp0s25 proto dhcp metric 100 169.254.0.0/16 dev enp0s25 scope link metric 1000 192.168.1.0/24 dev enp0s25 proto kernel scope link src 192.168.1.169 metric 100 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE IP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH enp0s25 ethernet connected full limited /org/freedesktop/NetworkManager/Devices/2 Wired connection 1 cb8f8bbb-c98f-3fcd-8212-fdf5d6425ab1 /org/freedesktop/NetworkManager/ActiveConnection/1 wlp3s0 wifi disconnected limited limited /org/freedesktop/NetworkManager/Devices/3 -- -- -- lo loopback unmanaged unknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.16.0 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1833512/+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 1833498] Re: Upgrading evince always breaks djvu support
Thanks, that confirms what was mentioned on the external pages you references, djvulibre-desktop is buggy/shipping a defintion that conflicts with the standard one, which is the main issue The single page case not working is because evince upstream decided those would be better opened as image than document, also according to them the single page format is old and deprecated, see https://bugzilla.gnome.org/show_bug.cgi?id=786511 Reassigning to djvulibre, the real issue is the first one ** Bug watch added: bugzilla.gnome.org/ #786511 https://bugzilla.gnome.org/show_bug.cgi?id=786511 ** Package changed: evince (Ubuntu) => djvulibre (Ubuntu) ** Changed in: djvulibre (Ubuntu) Status: Incomplete => New ** Summary changed: - Upgrading evince always breaks djvu support + djvulibre mimetype definition is incorrect and not needed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1833498 Title: djvulibre mimetype definition is incorrect and not needed Status in djvulibre package in Ubuntu: New Bug description: Every time I upgrade evince (as part of "sudo apt update; sudo apt upgrade") I have to remember to edit the file /usr/lib/x86_64-linux- gnu/evince/4/backends/djvudocument.evince-backend and add "image/vnd.djvu" to the end of MimeType list. If I don't do this then evince is unable to view djvu files. Please add "image/vnd.djvu" to MimeType in the official version of this file so that I (and presumably all other millions of Ubuntu Linux users, who are too lazy to open a bugreport for it) don't have to edit it manually. Thank you. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/djvulibre/+bug/1833498/+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 1833116] Re: chtmax98090 not working out of the box
** Changed in: alsa-driver (Ubuntu) Status: New => Confirmed -- 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/1833116 Title: chtmax98090 not working out of the box Status in alsa-driver package in Ubuntu: Confirmed Bug description: chtmax98090 intel HD audio device doesn't work out of the box after installing ubuntu (from 14.04 to 18.04). It shows "Dummy Output" on audio devices. Audio options shows device and it works if I do this: git clone https://github.com/plbossart/UCM.git cd UCM cp -r chtmax98090/ /usr/share/alsa/ucm/ alsactl store It would be great if there were a solution to make it works out of the box. The device (Chromebook Acer CB3-111 has it's end of life for chromeOS in July-August, so I suppose more people with this device will change OS perhaps to Ubuntu). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-21-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jaime 1293 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jun 17 20:32:35 2019 InstallationDate: Installed on 2019-06-17 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/18/2014 dmi.bios.vendor: coreboot dmi.chassis.type: 3 dmi.chassis.vendor: GOOGLE dmi.modalias: dmi:bvncoreboot:bvr:bd08/18/2014:svnGOOGLE:pnGnawty:pvr1.0:cvnGOOGLE:ct3:cvr: dmi.product.name: Gnawty dmi.product.version: 1.0 dmi.sys.vendor: GOOGLE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1833116/+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 1830422] Re: Shell boxpointer menus don't have scroll buttons when they exceed the screen height
@Dmytro, the issue is not with the library but with the indicator, you
can report to upstream on https://github.com/ubuntu/gnome-shell-
extension-appindicator
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1830422
Title:
Shell boxpointer menus don't have scroll buttons when they exceed the
screen height
Status in gnome-shell package in Ubuntu:
Opinion
Status in gnome-shell-extension-appindicator package in Ubuntu:
Confirmed
Bug description:
I am using appindicator-1.0 in conjunction with Gtk+2.0 menu. Menu
consist of constant items and many dynamically added items. If the
screen pixel resolution is not so good as it must be then the last
menu items are not visible. Ubuntu 16.04 automatically add top and
bottom bars with "^" and "v" arrows to scroll menu when mouse pointer
is over these bars. But in Linux Ubuntu 18.04 (and 19.04 too) such
scrolling bars are not appearing.
On the other hand menu scrolling is working fine anywhere into usual
GTK window with menu bar (without using appindicator). Ubuntu 16.04
and Ubuntu 18.04 use the same 12.10.1 libappindicator version.
Here is the test c program which illustrates the issue. It works fine
in Linux Ubuntu 16.04 and has the described above problem in Linux
18.04:
#include
#include
#define LOGO_PNG "/home/super/my-project/menu-test/logo.png"
AppIndicator* c_indicator;
GtkWidget* c_menu;
void menu_quit_cb(GtkMenuItem* menuitem, gpointer user_data)
{
gtk_main_quit();
}
int main(int argc, char *argv[])
{
gtk_init(, );
int i;
GtkWidget* item;
char title[128];
c_menu = gtk_menu_new();
item = gtk_menu_item_new_with_label("Quit");
g_signal_connect(item, "activate", G_CALLBACK(menu_quit_cb), NULL);
gtk_menu_shell_append(GTK_MENU_SHELL(c_menu), item);
gtk_widget_show(item);
gtk_menu_shell_append(GTK_MENU_SHELL(c_menu),
gtk_separator_menu_item_new());
for (i = 1; i <= 100; ++i) {
snprintf(title, sizeof(title), "Item #%03u", i);
item = gtk_menu_item_new_with_label(title);
gtk_menu_shell_append(GTK_MENU_SHELL(c_menu), item);
gtk_widget_show(item);
}
//
c_indicator = app_indicator_new("Menu Test", LOGO_PNG,
APP_INDICATOR_CATEGORY_APPLICATION_STATUS);
app_indicator_set_status(c_indicator, APP_INDICATOR_STATUS_ACTIVE);
app_indicator_set_icon(c_indicator, LOGO_PNG);
app_indicator_set_menu(c_indicator, GTK_MENU(c_menu));
gtk_main();
return 0;
}
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libappindicator1 12.10.1+18.04.20180322.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18
Uname: Linux 4.15.0-50-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri May 24 21:15:59 2019
InstallationDate: Installed on 2018-07-03 (325 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: libappindicator
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1830422/+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 1833555] Re: Add OEM->Family
** Changed in: ubuntu-report (Ubuntu) Importance: Undecided => Low ** Changed in: ubuntu-report (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-report in Ubuntu. https://bugs.launchpad.net/bugs/1833555 Title: Add OEM->Family Status in ubuntu-report package in Ubuntu: Confirmed Bug description: Some OEM store the commercial name of the product into the Family field of the system information record of smbios. Please add this fied to ubuntu-report. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-report 1.5.1 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jun 20 14:49:35 2019 Dependencies: gcc-9-base 9.1.0-4ubuntu1 libc6 2.29-0ubuntu2 libgcc1 1:9.1.0-4ubuntu1 libidn2-0 2.0.5-1 libunistring2 0.9.10-1ubuntu2 InstallationDate: Installed on 2014-07-15 (1801 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520) SourcePackage: ubuntu-report UpgradeStatus: Upgraded to eoan on 2018-03-24 (452 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-report/+bug/1833555/+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 1827842] Re: pulseaudio should not load module-x11-bell in gnome-shell
Could you provide the details asked in the previous comment? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1827842 Title: pulseaudio should not load module-x11-bell in gnome-shell Status in pulseaudio package in Ubuntu: Triaged Bug description: The package `pulseaudio` installs a startup script in `/etc/xdg/autostart/pulseaudio.desktop`, which itself runs `/usr/bin/start-pulseaudio-x11`, which loads a number of x11 related modules in `pulseaudio`. One of these modules is `module-x11-bell`, which makes `pulseaudio` play a sound each time a system bell is emitted (usually by terminal applications, such as bash or vim). This is redundant with gnome-shell, which is also able to handle the system bell (through the gsetting key `org.gnome.desktop.sound event-sounds`). The gnome system bell is directly configurable by the user (Settings > Sound), so it should be preferred over pulseaudio's own system bell. I suggest to patch the `/usr/bin/start-pulseaudio-x11`, to avoid loading `start-pulseaudio-x11` if it detects it is running in Gnome Shell (e.g. if GNOME_SHELL_SESSION_MODE is set). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1827842/+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 1832138] Re: Login screen never appears on vmwgfx using bionic kernel 4.15
** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: mutter (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: linux-hwe (Ubuntu Disco) Importance: Undecided Status: New ** Changed in: linux-hwe (Ubuntu Disco) Status: New => Triaged ** Changed in: linux-hwe (Ubuntu Disco) Status: Triaged => Invalid ** Changed in: mutter (Ubuntu Disco) Status: New => Invalid ** Changed in: linux (Ubuntu Disco) Status: New => Fix Released -- 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/1832138 Title: Login screen never appears on vmwgfx using bionic kernel 4.15 Status in linux package in Ubuntu: Invalid Status in linux-hwe package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Status in linux-hwe source package in Bionic: Fix Released Status in mutter source package in Bionic: In Progress Status in linux source package in Disco: Fix Released Status in linux-hwe source package in Disco: Invalid Status in mutter source package in Disco: Invalid Status in linux source package in Eoan: Invalid Status in linux-hwe source package in Eoan: Invalid Status in mutter source package in Eoan: Invalid Bug description: [Impact] With most recent version of mutter installed. If running kernel is in the 4.15 serie (using the vmwgfx video kernel driver) and if the login screen uses wayland, then the login prompt doesn't appears. All we see is the purple background with ubuntu in white at the bottom, nothing else. The vmwgfx driver in kernels prior to 4.17 reported bogus timestamps using the wrong clock. This would lead us to wait forever (or at least 49 years) before rendering the next frame. There's no decisive way to know this kernel bug is going to happen before it does so just detect timestamps which are obviously going to cause freezes and ignore them. [Test case] 1) Use Virtualbox or VMware ESxi (if you have the infra) 1.1) [virtualbox] Make sure in the VM setting that the display uses 'VMSVGA' which will force the OS to pick 'vmwgfx' video kernel driver. You can confirm with 'lspci -nnvv' command. 2) Deploy a VM with Ubuntu 18.04.1 (which come w/ 4.15) 4) apt-get dist-upgrade 5) Reboot with 4.15 it will fails with hwe kernel 4.18 it will work as expected. # workaround [Potential regression] Low, it should fix vmwgfx and stop using the wrong clock. A test kernel (pre-sru) has been made available to impact users for them to test and conclude it works. It does work as expected, and no regression has been found during the pre-sru testing phase. As per commit description: " This should be transparent to to user space, as long as it doesn't compare the time against the result of gettimeofday(). " [Other informations] upstream fix: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.2-rc5=37efe80ce85f [Original description] I'm running Ubuntu 18.04.2 desktop in a virtual machine under VMWare Fusion Pro V11.1.0 on MacOS Mojave 10.14.5, all on a 15inch 2018 Macbook Pro. I've been running this Ubuntu 18.04.2 VM without problem for many months without problem. Yesterday, I did 'sudo apt update; sudo apt upgrade'. Upon rebooting, the system hangs immediately after displaying the splash screen. I never see a login screen. And I can't use Ctrl+Alt+F2 to navigate to a console/tty login. I can SSH into the system however. I've found that I can work around the hang/freeze if I uncomment the following line in /etc/gdm3/custom.conf; #WaylandEnable=false After uncommenting the WaylandEnable=false line and rebooting, then I see the login prompt as expected and I can then log in and use the system normally again. After the 'apt upgrade' my system is running linux kernel 4.15.0-51, as shown in this 'uname -a' output; Linux ubuntuvm1 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux lsb_release -a output; No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.2 LTS Release: 18.04 Codename: bionic ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 Uname: Linux 4.15.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompositorRunning: None Date: Sun Jun 9 12:38:37 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate:
[Desktop-packages] [Bug 1832792] Re: App-switcher icons too small with hidpi (3000x2000) monitor
** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-shell (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1832792 Title: App-switcher icons too small with hidpi (3000x2000) monitor Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Triaged Bug description: I've reported this upstream (https://gitlab.gnome.org/GNOME/gnome- shell/issues/1370), but given that this is an important part of the Ubuntu desktop and that you're providing some patches for improving the X11 experience with hidpi monitors, I'm notifying about the issue here too. It could be related to my previous similar report for fractional scaling resolutions: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1831161. But I'm not sure. Besides, fractional scaling is an experimental feature while 2x is not. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1832792/+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 1826290] Re: geoclue mozilla location api key rate limited
(seems like GNOME got it somehow resolved for now,
https://gitlab.gnome.org/Teams/Board/issues/97 mentions it)
** Bug watch added: gitlab.gnome.org/Teams/Board/issues #97
https://gitlab.gnome.org/Teams/Board/issues/97
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to geoclue-2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1826290
Title:
geoclue mozilla location api key rate limited
Status in geoclue-2.0 package in Ubuntu:
Triaged
Bug description:
I am using Ubuntu 19.04
geoclue version: 0.12.99-4ubuntu2
geoclue2 version: 2.5.2-1ubuntu1
The key used by geoclue in ubuntu to access the mozilla location
service appears to be rate limited.
Here's the relevant lines in /etc/geoclue/geoclue.conf
# URL to the wifi geolocation service. The key can currenty be anything, just
# needs to be present but that is likely going to change in future.
url=https://location.services.mozilla.com/v1/geolocate?key=geoclue
The comment is wrong, using an invalid key gives a 400 error.
$ curl https://location.services.mozilla.com/v1/geolocate\?key=random_key
{"error":{"code":400,"message":"Missing or invalid API
key.","errors":[{"domain":"usageLimits","message":"Missing or invalid API
key.","reason":"keyInvalid"}]}}%
Using the current key gives a limit reached error
$ curl https://location.services.mozilla.com/v1/geolocate\?key=geoclue
{"error":{"code":403,"message":"You have exceeded your daily
limit.","errors":[{"domain":"usageLimits","message":"You have exceeded your
daily limit.","reason":"dailyLimitExceeded"}]}}%
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/geoclue-2.0/+bug/1826290/+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 1826290] Re: geoclue mozilla location api key rate limited
Is anyone still getting the issue? It seems to work fine here now, GNOME
was also discussing the issue so maybe they got the quota increased?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to geoclue-2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1826290
Title:
geoclue mozilla location api key rate limited
Status in geoclue-2.0 package in Ubuntu:
Triaged
Bug description:
I am using Ubuntu 19.04
geoclue version: 0.12.99-4ubuntu2
geoclue2 version: 2.5.2-1ubuntu1
The key used by geoclue in ubuntu to access the mozilla location
service appears to be rate limited.
Here's the relevant lines in /etc/geoclue/geoclue.conf
# URL to the wifi geolocation service. The key can currenty be anything, just
# needs to be present but that is likely going to change in future.
url=https://location.services.mozilla.com/v1/geolocate?key=geoclue
The comment is wrong, using an invalid key gives a 400 error.
$ curl https://location.services.mozilla.com/v1/geolocate\?key=random_key
{"error":{"code":400,"message":"Missing or invalid API
key.","errors":[{"domain":"usageLimits","message":"Missing or invalid API
key.","reason":"keyInvalid"}]}}%
Using the current key gives a limit reached error
$ curl https://location.services.mozilla.com/v1/geolocate\?key=geoclue
{"error":{"code":403,"message":"You have exceeded your daily
limit.","errors":[{"domain":"usageLimits","message":"You have exceeded your
daily limit.","reason":"dailyLimitExceeded"}]}}%
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/geoclue-2.0/+bug/1826290/+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 1788005] Re: print-playing-formats %aa and %aA report wrong value
** Changed in: rhythmbox Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1788005 Title: print-playing-formats %aa and %aA report wrong value Status in Rhythmbox: New Status in rhythmbox package in Ubuntu: Triaged Bug description: These formats incorrectly supply the value of the track artist, instead of the album artist. To fix this in 3.4.2 (Ubuntu 18.04), edit remote/dbus/rb-client.c lines 301 and 308 to say "xesam:albumArtist" instead of "xesam:artist". In 3.3 (Ubuntu 16.04) the corresponding lines are 288 and 295. To manage notifications about this bug go to: https://bugs.launchpad.net/rhythmbox/+bug/1788005/+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 1828884] Re: [META] Handling Japanese new era "令和 (Reiwa)"
Looks like noto sources now have the right glyphs (since their April 9 release, actually). It will need an update both in Debian and Ubuntu. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gucharmap in Ubuntu. https://bugs.launchpad.net/bugs/1828884 Title: [META] Handling Japanese new era "令和 (Reiwa)" Status in Poppler: New Status in fonts-noto-cjk package in Ubuntu: New Status in gucharmap package in Ubuntu: New Status in icu package in Ubuntu: New Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice-l10n package in Ubuntu: Fix Released Status in mozc package in Ubuntu: Fix Released Status in openjdk-8 package in Ubuntu: Fix Released Status in poppler-data package in Ubuntu: New Status in unicode-data package in Ubuntu: Fix Released Status in gnome-characters source package in Xenial: New Status in gucharmap source package in Xenial: New Status in icu source package in Xenial: New Status in libreoffice source package in Xenial: Fix Released Status in libreoffice-l10n source package in Xenial: Fix Released Status in mozc source package in Xenial: Fix Released Status in openjdk-8 source package in Xenial: New Status in poppler-data source package in Xenial: New Status in unicode-data source package in Xenial: New Status in fonts-noto-cjk source package in Bionic: New Status in gucharmap source package in Bionic: New Status in icu source package in Bionic: New Status in libreoffice source package in Bionic: Fix Released Status in libreoffice-l10n source package in Bionic: Fix Released Status in mozc source package in Bionic: Fix Released Status in openjdk-8 source package in Bionic: New Status in poppler-data source package in Bionic: New Status in unicode-data source package in Bionic: New Status in fonts-noto-cjk source package in Cosmic: New Status in gnome-characters source package in Cosmic: New Status in gucharmap source package in Cosmic: New Status in icu source package in Cosmic: New Status in libreoffice source package in Cosmic: Fix Released Status in libreoffice-l10n source package in Cosmic: Fix Released Status in mozc source package in Cosmic: Fix Released Status in openjdk-8 source package in Cosmic: New Status in poppler-data source package in Cosmic: New Status in unicode-data source package in Cosmic: New Status in fonts-noto-cjk source package in Disco: New Status in gnome-characters source package in Disco: New Status in gucharmap source package in Disco: New Status in icu source package in Disco: New Status in libreoffice source package in Disco: Fix Released Status in libreoffice-l10n source package in Disco: Fix Released Status in mozc source package in Disco: Fix Released Status in openjdk-8 source package in Disco: New Status in poppler-data source package in Disco: New Status in unicode-data source package in Disco: New Bug description: [Background] Many packages are affected by the requirement to support the new era "Reiwa" (令和） This is the meta bug to track packages that need fixes; which packages have already been SRUd to previous releases, how to prioritize the work needed, and general test cases for verifying that things are working as expected. [Impact] Users who run Ubuntu in Japanese. [Test cases] == Date conversion == On applications that support writing dates in long form, or with symbols to denote era (either in X00.00.00 format or in GG1G5G1G format (G- glyph; X- character): 1) Enable date formatting in each of the above formats that are supported (long form or symbols) 2) Type in '2019/05/01' to be formatted, verify that it shows as "令和1年5月1日" or "R1.05.01" 3) Type in '2019/04/30' to be formatted, verify that it shows as "平成31年4月30日" or "H31.4.30" == Date output == 1) Set date to 2019/05/01 2) Output date; verify that the year it is displayed as "令和元年" 3) Set date to 2019/04/30 4) Output date; verify that the year is diplayed as "平成31年" === Displaying formatted year for Japanese era with glibc === Run: LC_ALL=ja_JP.utf8 date +%EY -d 20190430 # previous era (should still work as before SRUs) or LC_ALL=ja_JP.utf8 date +%EY -d 20190501 # new era (should now correctly display the new era) == Character maps / font support == 1) Search for character "SQUARE ERA NAME" 2) Verify that the results include at least "SQUARE ERA NAME HEISEI" and "SQUARE ERA NAME REIWA" (there should also be Syouwa, Taisyou and Meizi), and that the glyphs are readable: - SQUARE ERA NAME HEISEI: ㍻ - SQUARE ERA NAME REIWA: 令和 (in a single glyph) Display of the Reiwa square glyph is font-specific; it may show simply as a empty square or a square with hex characters. If that is the case, the unicode data supports the new character, but the selected font does not include the new glyph. == Typing / input methods == 1)
[Desktop-packages] [Bug 1788005] Re: print-playing-formats %aa and %aA report wrong value
** Bug watch added: gitlab.gnome.org/GNOME/rhythmbox/issues #1688 https://gitlab.gnome.org/GNOME/rhythmbox/issues/1688 ** Also affects: rhythmbox via https://gitlab.gnome.org/GNOME/rhythmbox/issues/1688 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1788005 Title: print-playing-formats %aa and %aA report wrong value Status in Rhythmbox: Unknown Status in rhythmbox package in Ubuntu: Triaged Bug description: These formats incorrectly supply the value of the track artist, instead of the album artist. To fix this in 3.4.2 (Ubuntu 18.04), edit remote/dbus/rb-client.c lines 301 and 308 to say "xesam:albumArtist" instead of "xesam:artist". In 3.3 (Ubuntu 16.04) the corresponding lines are 288 and 295. To manage notifications about this bug go to: https://bugs.launchpad.net/rhythmbox/+bug/1788005/+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 1832138] Re: Login screen never appears on vmwgfx using bionic kernel 4.15
kernel-team archive ML: https://lists.ubuntu.com/archives/kernel-team/2019-June/101489.html ** Description changed: [Impact] With most recent version of mutter installed. If running kernel is in the 4.15 serie (using the vmwgfx video kernel driver) and if the login screen uses wayland, then the login prompt doesn't appears. All we see is the purple background with ubuntu in white at the bottom, nothing else. The vmwgfx driver in kernels prior to 4.17 reported bogus timestamps using the wrong clock. This would lead us to wait forever (or at least 49 years) before rendering the next frame. There's no decisive way to know this kernel bug is going to happen before it does so just detect timestamps which are obviously going to cause freezes and ignore them. [Test case] 1) Use Virtualbox or VMware ESxi (if you have the infra) 1.1) [virtualbox] Make sure in the VM setting that the display uses 'VMSVGA' which will force the OS to pick 'vmwgfx' video kernel driver. You can confirm with 'lspci -nnvv' command. 2) Deploy a VM with Ubuntu 18.04.1 (which come w/ 4.15) 4) apt-get dist-upgrade 5) Reboot with 4.15 it will fails with hwe kernel 4.18 it will work as expected. # workaround [Potential regression] Low, it should fix vmwgfx and stop using the wrong clock. A test kernel (pre-sru) has been made available to impact users for them to test and conclude it works. It does work as expected, and no regression has been found during the pre-sru testing phase. - - It can't be worse than actual situation where the login never appears. As per commit description: " This should be transparent to to user space, as long as it doesn't compare the time against the result of gettimeofday(). " [Other informations] upstream fix: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.2-rc5=37efe80ce85f [Original description] I'm running Ubuntu 18.04.2 desktop in a virtual machine under VMWare Fusion Pro V11.1.0 on MacOS Mojave 10.14.5, all on a 15inch 2018 Macbook Pro. I've been running this Ubuntu 18.04.2 VM without problem for many months without problem. Yesterday, I did 'sudo apt update; sudo apt upgrade'. Upon rebooting, the system hangs immediately after displaying the splash screen. I never see a login screen. And I can't use Ctrl+Alt+F2 to navigate to a console/tty login. I can SSH into the system however. I've found that I can work around the hang/freeze if I uncomment the following line in /etc/gdm3/custom.conf; #WaylandEnable=false After uncommenting the WaylandEnable=false line and rebooting, then I see the login prompt as expected and I can then log in and use the system normally again. After the 'apt upgrade' my system is running linux kernel 4.15.0-51, as shown in this 'uname -a' output; Linux ubuntuvm1 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux lsb_release -a output; No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.2 LTS Release: 18.04 Codename: bionic ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 Uname: Linux 4.15.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompositorRunning: None Date: Sun Jun 9 12:38:37 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2018-05-06 (399 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: VMware, Inc. VMware Virtual Platform ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic root=/dev/mapper/ubuntu--vg-root ro splash net.ifnames=0 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/13/2018 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd04/13/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. version.compiz: compiz N/A
[Desktop-packages] [Bug 1832651] Re: jackdbus fails to start: cannot allocate memory
** Tags added: id-5d0babe141a9fa1a8a1210f7 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/1832651 Title: jackdbus fails to start: cannot allocate memory Status in systemd: Fix Released Status in jackd2 package in Ubuntu: Invalid Status in systemd package in Ubuntu: Confirmed Status in jackd2 source package in Eoan: Invalid Status in systemd source package in Eoan: Confirmed Bug description: The `.log/jack/jackdbus.log` shows the following after trying to start/restart jack using "Ubuntu Studio Controls" (also tried using `jack_control start`): ERROR: Cannot lock down 82280346 byte memory area (Cannot allocate memory) This is a fresh install of Ubuntu Studio 19.04, installed via USB. The first thing I did after installing was check to see if jack was running, but unfortunately it's not working. The error would seem to indicate that I'm not in the `audio` group, however checking `groups` shows that I am in the audio group. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: jackd2 1.9.12~dfsg-2build1 ProcVersionSignature: Ubuntu 5.0.0-13.14-lowlatency 5.0.6 Uname: Linux 5.0.0-13-lowlatency x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Jun 12 18:13:25 2019 InstallationDate: Installed on 2019-06-12 (0 days ago) InstallationMedia: Ubuntu-Studio 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: jackd2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1832651/+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 1292041] Re: Lockscreen doesn't turn off the screen
Possible duplicates: Bug #1612010 and Bug #1594989 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1292041 Title: Lockscreen doesn't turn off the screen Status in OEM Priority Project: Fix Released Status in OEM Priority Project trusty series: Fix Released Status in Unity: Fix Released Status in gnome-screensaver package in Ubuntu: Invalid Status in unity package in Ubuntu: Fix Released Bug description: [ATTENTION] This bug report is strictly for lockscreen. When user activates lockscreen with Ctrl+Alt+L or Super+L shortcut or from indicator-session the screen should blank off after a couple seconds. The new Unity lock screen doesn't turn off the monitor screen. I can wait as long as 10 minutes after activating the lock screen and the monitor still doesn't turn off. Then when I unlock the screen and don't use mouse or keyboard monitor will turn off (it's about 5 seconds after unlocking). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1292041/+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 1292041] Re: Lockscreen doesn't turn off the screen
Same problem as everyone else: Locking the screen with Win+L turns off the monitors (I get "Signal lost" warnings on them) but after a minute or so, something turns them back on. xset q reports: DPMS (Energy Star): Standby: 0Suspend: 0Off: 0 DPMS is Enabled Monitor is On Note: The same happens when I force the monitors to turn off with xset dpms force off In the journal, I see these entries after shutting off the monitors at 13:57:51: Jun 21 13:58:16 linux01 /usr/lib/gdm3/gdm-x-session[2471]: (II) modeset(0): EDID vendor "HWP", prod id 12816 Jun 21 13:58:16 linux01 /usr/lib/gdm3/gdm-x-session[2471]: (II) modeset(0): Using hsync ranges from config file Jun 21 13:58:16 linux01 /usr/lib/gdm3/gdm-x-session[2471]: (II) modeset(0): Using vrefresh ranges from config file Jun 21 13:58:16 linux01 /usr/lib/gdm3/gdm-x-session[2471]: (II) modeset(0): Printing DDC gathered Modelines: Jun 21 13:58:16 linux01 /usr/lib/gdm3/gdm-x-session[2471]: (II) modeset(0): Modeline "1920x1200"x0.0 154.00 1920 1968 2000 2080 1200 1203 1209 1235 +hsync -vsync (74.0 kHz eP) ... Jun 21 13:58:19 linux01 gnome-shell[2611]: STACK_OP_RAISE_ABOVE: sibling window 0x54017c3 not in stack Jun 21 13:58:19 linux01 gnome-shell[2611]: STACK_OP_RAISE_ABOVE: sibling window 0x54017c3 not in stack Jun 21 13:58:19 linux01 gnome-shell[2611]: STACK_OP_RAISE_ABOVE: sibling window 0x54017c3 not in stack -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1292041 Title: Lockscreen doesn't turn off the screen Status in OEM Priority Project: Fix Released Status in OEM Priority Project trusty series: Fix Released Status in Unity: Fix Released Status in gnome-screensaver package in Ubuntu: Invalid Status in unity package in Ubuntu: Fix Released Bug description: [ATTENTION] This bug report is strictly for lockscreen. When user activates lockscreen with Ctrl+Alt+L or Super+L shortcut or from indicator-session the screen should blank off after a couple seconds. The new Unity lock screen doesn't turn off the monitor screen. I can wait as long as 10 minutes after activating the lock screen and the monitor still doesn't turn off. Then when I unlock the screen and don't use mouse or keyboard monitor will turn off (it's about 5 seconds after unlocking). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1292041/+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 1612010] Re: Lockscreen doesn't turn off the screen
Duplicate of Bug #1292041 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1612010 Title: Lockscreen doesn't turn off the screen Status in gnome-screensaver package in Ubuntu: Confirmed Bug description: Lockscreen doesn't turn off the screen (saw it via Bug # 1292041 now closed) Ctrl=Alt+L or Super+L shortcut works and blanks the screen requiring me to type my password again to activate session. However my System-Settings -> Brightness & Lock is set to: Turn screen off when inactive for: 30 minutes Lock: OFF Lock screen after: Screen turns off (is grayed out) Require my password when waking from suspend (unchecked and grayed out) I have dual monitors. Both are Samsung and this feature is highly intermittent, meaning sometimes it works and often it doesn't. For example it hasn't worked for days but I changed the System-Settings from 30-minutes to 1-min. and it started working without a reboot. Is it possible that a kernel update changes some value that alters the setting? Then when I change the time in the window it repopulates a value? I am on Ubuntu 16.04.1 but I have seen this issue for years now. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1612010/+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 1594989] Re: Turn off screen after n minutes does not work in Ubuntu 16.04
Duplicate of Bug #1292041 https://bugs.launchpad.net/ubuntu/+source /gnome-screensaver/+bug/1292041 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1594989 Title: Turn off screen after n minutes does not work in Ubuntu 16.04 Status in gnome-screensaver package in Ubuntu: Confirmed Bug description: After I upgraded to Ubuntu 16.04, the feature of turning off screen when inactive for a certain period of time, does not work. I have tested it several times, changing the duration, without any avail. This is happening in all the three machines I use. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1594989/+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 1833471] Re: Can not enable Wifi Hotspot
Good news. I created a new user profile and now it works. Would it be possible to delete a few files on the old profile (gnome control center) related to get the old profile working? thanks -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1833471 Title: Can not enable Wifi Hotspot Status in gnome-shell package in Ubuntu: New Bug description: Ubuntu 19.04 fresh upgrade Hotspot was working on Elitebook 740G2 on Ubuntu 16.04 was no longer working on Ubuntu 18.04 When Wifi is enabled, I can connect to wifi router. So wifi works When choosing "Turn on Wi-Fi Hotspot" it pops up the dialog box if I want to Turn on or Cancel, when choosing "Turn on" it crashes (Screen goes black) or it clears the "Visible Networks" box, a few seconds later is shows available networks again ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-control-center 1:3.32.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8 Uname: Linux 5.0.0-17-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jun 19 23:07:45 2019 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2015-07-19 (1431 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to disco on 2019-06-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1833471/+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 1833471] Re: Can not enable Wifi Hotspot
I do not think I have gnome shell extensions installed. nbeerli@galaxy3:~$ sudo apt remove gnome-shell-extensions Reading package lists... Done Building dependency tree Reading state information... Done Package 'gnome-shell-extensions' is not installed, so not removed 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. nbeerli@galaxy3:~$ Also no EasyScreenCase -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1833471 Title: Can not enable Wifi Hotspot Status in gnome-shell package in Ubuntu: New Bug description: Ubuntu 19.04 fresh upgrade Hotspot was working on Elitebook 740G2 on Ubuntu 16.04 was no longer working on Ubuntu 18.04 When Wifi is enabled, I can connect to wifi router. So wifi works When choosing "Turn on Wi-Fi Hotspot" it pops up the dialog box if I want to Turn on or Cancel, when choosing "Turn on" it crashes (Screen goes black) or it clears the "Visible Networks" box, a few seconds later is shows available networks again ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-control-center 1:3.32.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8 Uname: Linux 5.0.0-17-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jun 19 23:07:45 2019 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2015-07-19 (1431 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to disco on 2019-06-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1833471/+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 1833471] Re: Can not enable Wifi Hotspot
The error seems on the gnome-shell side, https://bbs.archlinux.org/viewtopic.php?id=232193 has a similar log ... do you have extensions installed? the 'EasyScreenCase' one? ** Package changed: gnome-control-center (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1833471 Title: Can not enable Wifi Hotspot Status in gnome-shell package in Ubuntu: New Bug description: Ubuntu 19.04 fresh upgrade Hotspot was working on Elitebook 740G2 on Ubuntu 16.04 was no longer working on Ubuntu 18.04 When Wifi is enabled, I can connect to wifi router. So wifi works When choosing "Turn on Wi-Fi Hotspot" it pops up the dialog box if I want to Turn on or Cancel, when choosing "Turn on" it crashes (Screen goes black) or it clears the "Visible Networks" box, a few seconds later is shows available networks again ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-control-center 1:3.32.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8 Uname: Linux 5.0.0-17-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jun 19 23:07:45 2019 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2015-07-19 (1431 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to disco on 2019-06-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1833471/+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 1833471] Re: Can not enable Wifi Hotspot
Here more info to that: nbeerli@nbeerli-galaxy3:~$ journalctl -b 0 |grep -A 5 -B 5 "Error looking up permission: GDBus.Error" Jun 21 12:34:30 nbeerli-galaxy3 dbus-daemon[1045]: [system] Activating via systemd: service name='net.reactivated.Fprint' unit='fprintd.service' requested by ':1.38' (uid=125 pid=1381 comm="/usr/bin/gnome-shell " label="unconfined") Jun 21 12:34:30 nbeerli-galaxy3 systemd[1]: Starting Fingerprint Authentication Daemon... Jun 21 12:34:30 nbeerli-galaxy3 dbus-daemon[1045]: [system] Successfully activated service 'net.reactivated.Fprint' Jun 21 12:34:30 nbeerli-galaxy3 systemd[1]: Started Fingerprint Authentication Daemon. Jun 21 12:34:30 nbeerli-galaxy3 gnome-shell[1381]: Getting invalid resource scale property Jun 21 12:34:30 nbeerli-galaxy3 gnome-shell[1381]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation Jun 21 12:34:30 nbeerli-galaxy3 gnome-shell[1381]: JS WARNING: [resource:///org/gnome/shell/ui/windowManager.js 1644]: reference to undefined property "MetaWindowXwayland" Jun 21 12:34:31 nbeerli-galaxy3 gnome-session-binary[1367]: Entering running state Jun 21 12:34:31 nbeerli-galaxy3 NetworkManager[1046]: [1561113271.4458] device (vmnet1): driver '(null)' does not support carrier detection. Jun 21 12:34:31 nbeerli-galaxy3 systemd-udevd[432]: Using default interface naming scheme 'v240'. Jun 21 12:34:31 nbeerli-galaxy3 NetworkManager[1046]: [1561113271.4461] device (vmnet1): driver 'unknown' does not support carrier detection. -- Jun 21 12:35:13 nbeerli-galaxy3 dbus-daemon[2043]: [session uid=1000 pid=2043] Successfully activated service 'org.gnome.evolution.dataserver.AddressBook9' Jun 21 12:35:13 nbeerli-galaxy3 systemd[2015]: Started Evolution address book service. Jun 21 12:35:13 nbeerli-galaxy3 dropbox.desktop[2401]: dropbox: load fq extension '/home/nbeerli/.dropbox-dist/dropbox-lnx.x86_64-74.4.115/cryptography.hazmat.bindings._openssl.cpython-37m-x86_64-linux-gnu.so' Jun 21 12:35:13 nbeerli-galaxy3 dropbox.desktop[2401]: dropbox: load fq extension '/home/nbeerli/.dropbox-dist/dropbox-lnx.x86_64-74.4.115/cryptography.hazmat.bindings._padding.cpython-37m-x86_64-linux-gnu.so' Jun 21 12:35:14 nbeerli-galaxy3 NetworkManager[1046]: [1561113314.0652] agent-manager: req[0x5561c27a58d0, :1.356/org.gnome.Shell.NetworkAgent/1000]: agent registered Jun 21 12:35:14 nbeerli-galaxy3 gnome-shell[2191]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation Jun 21 12:35:14 nbeerli-galaxy3 dropbox.desktop[2401]: dropbox: load fq extension '/home/nbeerli/.dropbox-dist/dropbox-lnx.x86_64-74.4.115/psutil._psutil_linux.cpython-37m-x86_64-linux-gnu.so' Jun 21 12:35:14 nbeerli-galaxy3 dropbox.desktop[2401]: dropbox: load fq extension '/home/nbeerli/.dropbox-dist/dropbox-lnx.x86_64-74.4.115/psutil._psutil_posix.cpython-37m-x86_64-linux-gnu.so' Jun 21 12:35:14 nbeerli-galaxy3 dropbox.desktop[2401]: dropbox: load fq extension '/home/nbeerli/.dropbox-dist/dropbox-lnx.x86_64-74.4.115/linuxffi.pthread._linuxffi_pthread.cpython-37m-x86_64-linux-gnu.so' Jun 21 12:35:14 nbeerli-galaxy3 dropbox.desktop[2401]: dropbox: load fq extension '/home/nbeerli/.dropbox-dist/dropbox-lnx.x86_64-74.4.115/cpuid.compiled._cpuid.cpython-37m-x86_64-linux-gnu.so' Jun 21 12:35:14 nbeerli-galaxy3 dropbox.desktop[2401]: dropbox: load fq extension '/home/nbeerli/.dropbox-dist/dropbox-lnx.x86_64-74.4.115/apex._apex.cpython-37m-x86_64-linux-gnu.so' Let me know if you need anything else -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1833471 Title: Can not enable Wifi Hotspot Status in gnome-control-center package in Ubuntu: Incomplete Bug description: Ubuntu 19.04 fresh upgrade Hotspot was working on Elitebook 740G2 on Ubuntu 16.04 was no longer working on Ubuntu 18.04 When Wifi is enabled, I can connect to wifi router. So wifi works When choosing "Turn on Wi-Fi Hotspot" it pops up the dialog box if I want to Turn on or Cancel, when choosing "Turn on" it crashes (Screen goes black) or it clears the "Visible Networks" box, a few seconds later is shows available networks again ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-control-center 1:3.32.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8 Uname: Linux 5.0.0-17-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jun 19 23:07:45 2019 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2015-07-19 (1431 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to disco on 2019-06-19 (0 days ago) To manage notifications about this bug go to:
[Desktop-packages] [Bug 1833471] Re: Can not enable Wifi Hotspot
Thanks, the warnings give some clue on what to log for in the log, the journal has those lines but they are cut 'Jun 20 18:34:42 nbeerli-galaxy3 NetworkManager[1034]: [1561048482.7121] agent-manager: req[0x55ee590c7300, :1.305/org.g Jun 20 18:34:43 nbeerli-galaxy3 gnome-shell[3124]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFou' -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1833471 Title: Can not enable Wifi Hotspot Status in gnome-control-center package in Ubuntu: Incomplete Bug description: Ubuntu 19.04 fresh upgrade Hotspot was working on Elitebook 740G2 on Ubuntu 16.04 was no longer working on Ubuntu 18.04 When Wifi is enabled, I can connect to wifi router. So wifi works When choosing "Turn on Wi-Fi Hotspot" it pops up the dialog box if I want to Turn on or Cancel, when choosing "Turn on" it crashes (Screen goes black) or it clears the "Visible Networks" box, a few seconds later is shows available networks again ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-control-center 1:3.32.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8 Uname: Linux 5.0.0-17-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jun 19 23:07:45 2019 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2015-07-19 (1431 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to disco on 2019-06-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1833471/+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 1786344] Re: Default IBus input method ignored in live session
** Merge proposal linked: https://code.launchpad.net/~gunnarhj/ubuntu/+source/gnome-settings-daemon/+git/gnome-settings-daemon/+merge/369154 -- 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/1786344 Title: Default IBus input method ignored in live session Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in gnome-settings-daemon source package in Bionic: In Progress Bug description: [Impact] If you * start your computer with a bootable USB stick or DVD with the 18.04.2 desktop ISO * wait until Ubiquity's welcome screen shows up (only possible on systems with legacy BIOS; bug #1766047) * select a language which requires an input method for typing * click the "Try Ubuntu" button no IBus method is made easily available via the input source indicator in the session you enter. If you for instance select zh_CN as language and "Try Ubuntu", you would expect to enter a session with the "Intelligent Pinyin" method included among the available input sources. The proposed fix should ensure that an IBus method is always available in "live sessions" in languages which are prepared for it. [Test Case] 1. Install ibus-libpinyin and make sure that "Intelligent Pinyin" is not included among your available input sources. 2. Generate the Chinese locale: sudo locale-gen zh_CN.UTF-8 3. Add to ~/.profile this line: export LC_CTYPE=zh_CN.UTF-8 4. Remove the gnome-settings-daemon stamp file: rm ~/.local/share/gnome-settings-daemon/input-sources-converted 5. Log out and log in again. => Find that the "Intelligent Pinyin" method was not added (since the sources already in the list prevented it from being added). 6. Install gnome-settings-daemon from bionic-proposed. 7. Repeat step 4 and 5. => Find that the "Intelligent Pinyin" method was added. [Regression Potential] The proposed upload includes a small change which specifically addresses the issue as described above. I find that the risk for adverse side effects is low. [Original description] Ubuntu 18.10 iso (2018.8.7), select Simplified Chinese for booting, can't input Chinese character. From Settings -> Regions and Languages, selected Intelligent Pinyin, also could not input Chinese. --- 18.10 镜像（2018.8.7）选择简体中文开机，无法输入中文。由 Settings -> Regions and Languages，选择 智能拼音，也无法输入中文。 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1786344/+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 1786344] Re: Default IBus input method ignored in live session
I have tested the daily build ISO from this morning UTC. If I enter Ubiquity's welcome screen, select zh_CN from there and "Try Ubuntu", "Intelligent Pinyin" is now - unlike before - active in the resulting session, and I can select it via the input source indicator or + and start inputting Chinese instantly. Also tried ja_JP, also with a positive result. If I enter the isolinux menu, select e.g. ja_JP from there and "Try Ubuntu before installing", it looks exactly as previously, i.e. "Mozc" is available together with one Japanse XKB layout. (No regression, in other words.) Due to these positive results I will submit a bionic merge proposal with this change, and with the goal to have this improvement make it to the 18.04.3 ISO. ** Changed in: gnome-settings-daemon (Ubuntu Bionic) Status: Confirmed => In Progress -- 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/1786344 Title: Default IBus input method ignored in live session Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in gnome-settings-daemon source package in Bionic: In Progress Bug description: [Impact] If you * start your computer with a bootable USB stick or DVD with the 18.04.2 desktop ISO * wait until Ubiquity's welcome screen shows up (only possible on systems with legacy BIOS; bug #1766047) * select a language which requires an input method for typing * click the "Try Ubuntu" button no IBus method is made easily available via the input source indicator in the session you enter. If you for instance select zh_CN as language and "Try Ubuntu", you would expect to enter a session with the "Intelligent Pinyin" method included among the available input sources. The proposed fix should ensure that an IBus method is always available in "live sessions" in languages which are prepared for it. [Test Case] 1. Install ibus-libpinyin and make sure that "Intelligent Pinyin" is not included among your available input sources. 2. Generate the Chinese locale: sudo locale-gen zh_CN.UTF-8 3. Add to ~/.profile this line: export LC_CTYPE=zh_CN.UTF-8 4. Remove the gnome-settings-daemon stamp file: rm ~/.local/share/gnome-settings-daemon/input-sources-converted 5. Log out and log in again. => Find that the "Intelligent Pinyin" method was not added (since the sources already in the list prevented it from being added). 6. Install gnome-settings-daemon from bionic-proposed. 7. Repeat step 4 and 5. => Find that the "Intelligent Pinyin" method was added. [Regression Potential] The proposed upload includes a small change which specifically addresses the issue as described above. I find that the risk for adverse side effects is low. [Original description] Ubuntu 18.10 iso (2018.8.7), select Simplified Chinese for booting, can't input Chinese character. From Settings -> Regions and Languages, selected Intelligent Pinyin, also could not input Chinese. --- 18.10 镜像（2018.8.7）选择简体中文开机，无法输入中文。由 Settings -> Regions and Languages，选择 智能拼音，也无法输入中文。 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1786344/+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 1833471] Re: Can not enable Wifi Hotspot
Here the output from the terminal. Sorry about the other question: Its the whole session. It varies. Sometimes it gets be back to the login page nbeerli@nbeerli-galaxy3:~$ gnome-control-center (gnome-control-center:18961): network-cc-panel-WARNING **: 11:26:23.739: Could not get secrets: No agents were available for this request. (gnome-control-center:18961): network-cc-panel-WARNING **: 11:26:23.739: Could not get secrets: No agents were available for this request. (gnome-control-center:18961): network-cc-panel-WARNING **: 11:26:23.755: Could not get secrets: No agents were available for this request. (gnome-control-center:18961): network-cc-panel-WARNING **: 11:26:48.726: Could not get secrets: Timeout was reached nbeerli@nbeerli-galaxy3:~$ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1833471 Title: Can not enable Wifi Hotspot Status in gnome-control-center package in Ubuntu: Incomplete Bug description: Ubuntu 19.04 fresh upgrade Hotspot was working on Elitebook 740G2 on Ubuntu 16.04 was no longer working on Ubuntu 18.04 When Wifi is enabled, I can connect to wifi router. So wifi works When choosing "Turn on Wi-Fi Hotspot" it pops up the dialog box if I want to Turn on or Cancel, when choosing "Turn on" it crashes (Screen goes black) or it clears the "Visible Networks" box, a few seconds later is shows available networks again ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-control-center 1:3.32.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8 Uname: Linux 5.0.0-17-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jun 19 23:07:45 2019 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2015-07-19 (1431 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to disco on 2019-06-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1833471/+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 1833558] Re: gnome-shell crashed with SIGSEGV in meta_monitor_manager_get_monitor_for_connector() from
** Tags added: cosmic disco -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1833558 Title: gnome-shell crashed with SIGSEGV in meta_monitor_manager_get_monitor_for_connector() from Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/6651d911f833729ccc39cf01ed5e393b95cb0c3f gnome shell crashes when I go to Settings -> Devices -> Displays ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.4-0ubuntu18.04.1 ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-21-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Wed Jun 19 11:01:41 2019 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2016-04-29 (1146 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcCmdline: /usr/bin/gnome-shell SegvAnalysis: Segfault happened at: 0x7f49b8116bf0 :mov0x18(%rax),%eax PC (0x7f49b8116bf0) ok source "0x18(%rax)" (0x0018) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: meta_monitor_manager_get_monitor_for_connector () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0 ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6 () at /usr/lib/libgjs.so.0 () at /usr/lib/libgjs.so.0 Title: gnome-shell crashed with SIGSEGV in meta_monitor_manager_get_monitor_for_connector() UpgradeStatus: Upgraded to bionic on 2018-08-04 (319 days ago) UserGroups: adm cdrom dip docker kvm libvirt libvirtd lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1833558/+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 1833471] Re: Can not enable Wifi Hotspot
The journal has no settings error, do you remember at what time you triggered the bug? Could you start gnome-control-center from a command line, activate hotspot and see if any warning/error is displayed on the standard output? You also didn't answer the part about the screen going back, is that the settings page or session? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1833471 Title: Can not enable Wifi Hotspot Status in gnome-control-center package in Ubuntu: Incomplete Bug description: Ubuntu 19.04 fresh upgrade Hotspot was working on Elitebook 740G2 on Ubuntu 16.04 was no longer working on Ubuntu 18.04 When Wifi is enabled, I can connect to wifi router. So wifi works When choosing "Turn on Wi-Fi Hotspot" it pops up the dialog box if I want to Turn on or Cancel, when choosing "Turn on" it crashes (Screen goes black) or it clears the "Visible Networks" box, a few seconds later is shows available networks again ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-control-center 1:3.32.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8 Uname: Linux 5.0.0-17-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jun 19 23:07:45 2019 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2015-07-19 (1431 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to disco on 2019-06-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1833471/+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 1824073] Re: USB stick isn't mounted automatically
** Changed in: oem-priority/xenial Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1824073 Title: USB stick isn't mounted automatically Status in OEM Priority Project: Confirmed Status in OEM Priority Project xenial series: Confirmed Status in udisks2 package in Ubuntu: Fix Released Status in udisks2 source package in Xenial: New Bug description: [Impact] USB stick isn't mounted automatically. Auto-mount function fails. [Test Case] 1) Plug USB stick and check if USB stick is mounted automatically. 2) Umount USB stick 3) Unplug USB stick 4) Go to 1) --- If the error message below appears, auto-mount function will fail. systemd-udevd[2690]: inotify_add_watch(9, /dev/sda, 10) failed: No such file or directory Error Message: 1. when auto-mount fails: kernel: [ 175.661572] usb 2-2.3.3: USB disconnect, device number 6 systemd-udevd[2690]: inotify_add_watch(9, /dev/sda, 10) failed: No such file or directory org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: drive_changed org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1bd6810 org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: volume_removed org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1b8c3d0 kernel: [ 222.843326] usb 2-2.3.3: new SuperSpeed USB device number 7 using xhci_hcd org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: drive_changed org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1bd6810 org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: volume_added org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1b8c470 2. when auto-mount works: kernel: [ 124.313084] usb 2-2.3.3: USB disconnect, device number 5 org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: volume_changed org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1b8c330 org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: drive_disconnected org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1b9dea0 org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: volume_removed org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1b8c330 kernel: [ 136.531496] usb 2-2.3.3: new SuperSpeed USB device number 6 using xhci_hcd org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: drive_changed org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1bd6810 org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: drive_connected org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1bd6810 org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: volume_added org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1b8c3d0 org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: in handle_volume_mount udisksd[2274]: Mounted /dev/sda1 at /media/u/U on behalf of uid 1001 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1824073/+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
