[Desktop-packages] [Bug 1719038] Re: X Server crashes during log in VM since 16.04.2
** Also affects: spice (Ubuntu) Importance: Undecided Status: New -- 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/1719038 Title: X Server crashes during log in VM since 16.04.2 Status in X.Org X server: Unknown Status in qemu package in Ubuntu: New Status in spice package in Ubuntu: New Status in xorg package in Ubuntu: Confirmed Bug description: If I change screen resolution in my VM with Kubuntu 16.04.3 and then make log off and then log on X server is crashes doesn't able me to log in. Please, look in Xorg.0.log.old for backtrace. Also the appropriate report on freedesktop.org: https://bugs.freedesktop.org/show_bug.cgi?id=102554 Host: Kubuntu 17.04 Linux 4.13.2 libvirt-bin 3.6.0 qemu 2.10 Guest: Kubuntu 16.04.3 Linux 4.10.0-35-generic xserver-xorg-video-qxl 0.1.4-3ubuntu3 xserver-common 1.18.4-0ubuntu0.3 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xserver-xorg (not installed) ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-35-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: KDE Date: Sat Sep 23 01:27:49 2017 InstallationDate: Installed on 2016-09-16 (371 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1719038/+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 1482961] Re: Messed up icon sizes for .desktop files
[Expired for nautilus (Ubuntu) because there has been no activity for 60 days.] ** Changed in: nautilus (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1482961 Title: Messed up icon sizes for .desktop files Status in nautilus package in Ubuntu: Expired Bug description: .desktop entries showing the original size of the image files as icon. A screenshot is attached. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: nautilus 1:3.14.2-0ubuntu9.1 ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Aug 9 13:30:38 2015 GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'group', 'where', 'mime_type', 'owner', 'permissions']" InstallationDate: Installed on 2012-06-22 (1142 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) SourcePackage: nautilus UpgradeStatus: Upgraded to vivid on 2015-08-04 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1482961/+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 1518740] Re: Filesystem type not shown (NTFS or FAT32)
[Expired for nautilus (Ubuntu) because there has been no activity for 60 days.] ** Changed in: nautilus (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1518740 Title: Filesystem type not shown (NTFS or FAT32) Status in nautilus package in Ubuntu: Expired Bug description: I have an external USB hard disk connected; I think it's an NTFS or amybe FAT32 filesystem, certainly not an ext* one. I right-click on it on the left panel of Nautilus and select Properties (or I open it, right-click on the background of the right panel and select "properties", it's the same). Result: see the screenshot. It says: "Filesystem type:" and nothing follows. It should indicate the type of filesystem. Pathetic, as usual with Nautilus. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: nautilus 1:3.14.2-0ubuntu9.1 ProcVersionSignature: Ubuntu 3.19.0-33.38-generic 3.19.8-ckt7 Uname: Linux 3.19.0-33-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1.8 Architecture: amd64 CurrentDesktop: Unity Date: Sun Nov 22 19:05:34 2015 GsettingsChanges: b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2013-10-11 (772 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: nautilus UpgradeStatus: Upgraded to vivid on 2015-08-15 (98 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1518740/+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 1762801] Re: Xwayland crashed with signal 7 in XkbDeviceApplyKeymap()
[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg-server (Ubuntu) Status: Incomplete => Expired -- 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/1762801 Title: Xwayland crashed with signal 7 in XkbDeviceApplyKeymap() Status in xorg-server package in Ubuntu: Expired Bug description: none ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: xwayland 2:1.19.6-1ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CompositorRunning: None CrashCounter: 1 CurrentDesktop: GNOME-Greeter:GNOME Date: Sat Apr 7 17:18:23 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExecutablePath: /usr/bin/Xwayland GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Haswell-ULT Integrated Graphics Controller [1043:13ed] InstallationDate: Installed on 2018-03-01 (40 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180301) MachineType: ASUSTeK COMPUTER INC. S301LA ProcCmdline: /usr/bin/Xwayland :1024 -rootless -terminate -accessx -core -listen 4 -listen 5 -displayfd 6 ProcEnviron: LANGUAGE=es_BO:es PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_BO.UTF-8 SHELL=/bin/false ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=47cb83ff-b68f-4365-9a97-07b0b4723c16 ro quiet splash vt.handoff=1 Signal: 7 SourcePackage: xorg-server StacktraceTop: ?? () XkbDeviceApplyKeymap () ?? () ?? () ?? () Title: Xwayland crashed with signal 7 in XkbDeviceApplyKeymap() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 08/19/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: S301LA.205 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: S301LA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrS301LA.205:bd08/19/2013:svnASUSTeKCOMPUTERINC.:pnS301LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnS301LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: S dmi.product.name: S301LA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1762801/+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 1737614] Re: Low sound volume with Sunrise Point-LP HD Audio (ALC3227) in HP 15-BS576TX laptop
Still here with Ubuntu 18.04 on ThinkPad P51s $ cat /proc/asound/card*/codec* | grep Codec Codec: Realtek ALC298 Codec: Intel Kabylake HDMI $ sudo lspci -vvv | grep -A 40 -i audio 00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21) Subsystem: Lenovo Sunrise Point-LP HD Audio Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- https://bugs.launchpad.net/bugs/1737614 Title: Low sound volume with Sunrise Point-LP HD Audio (ALC3227) in HP 15-BS576TX laptop Status in alsa-driver package in Ubuntu: Confirmed Bug description: I have a new laptop HP-15-BS576TX which has this Intel Corporation Sunrise Point-LP HD Audio. 00:1f.3 Audio device [0403]: Intel Corporation Sunrise Point-LP HD Audio [8086:9d71] (rev 21) The laptop sound works perfectly fine in Windows 10 with realtek drivers. However, in Ubuntu 17.10, the volume is significantly low, that I've to scroll the volume slider above 100% mark in pulseaudio to the maximum to get acceptable level of sound. I suspect the sound quality also is low (mono-like), may be not coming from all speakers (perhaps subwoofer exist for this model). Also alsamixer shows the speaker volume at the maximum. Details about the audio hardware are below: :~$ sudo lspci -vvv | grep -A 40 -i audio 00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21) (prog-if 80) Subsystem: Hewlett-Packard Company Device 832b Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- /proc/asound/card0/codec#0 <== Codec: Realtek ALC3227 ==> /proc/asound/card0/codec#2 <== Codec: Intel Kabylake HDMI :~$ aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC3227 Analog [ALC3227 Analog] Subdevices: 0/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 I have gone through Linux kernel sources ALSA and Snd-HDA lists and unable to find any optimizations for this laptop. Here is the relevant dmesg details: [ 15.502856] snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [ 16.310503] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC3227: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker [ 16.310506] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [ 16.310507] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [ 16.310508] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [ 16.310509] snd_hda_codec_realtek hdaudioC0D0:inputs: [ 16.310510] snd_hda_codec_realtek hdaudioC0D0: Mic=0x19 [ 16.310512] snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12 [ 16.451397] input: HDA Intel PCH Mic as /devices/pci:00/:00:1f.3/sound/card0/input9 [ 16.451451] input: HDA Intel PCH Headphone as /devices/pci:00/:00:1f.3/sound/card0/input10 [ 16.451496] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci:00/:00:1f.3/sound/card0/input11 [ 16.451538] input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci:00/:00:1f.3/sound/card0/input12 [ 16.451581] input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci:00/:00:1f.3/sound/card0/input13 [ 16.451624] input: HDA Intel PCH HDMI/DP,pcm=9 as /devices/pci:00/:00:1f.3/sound/card0/input14 [ 16.451687] input: HDA Intel PCH HDMI/DP,pcm=10 as /devices/pci:00/:00:1f.3/sound/card0/input15 Any further information needed, please let me know. Thank you. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 [modified: usr/share/alsa-base/alsa-info.sh] ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 NonfreeKernelModules: ndiswrapper ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: admin2018 1246 F pulseaudio CurrentDesktop: GNOME Date: Tue Dec 12 00:46:12 2017 InstallationDate: Installed on 2017-11-22 (19 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) PackageArchitecture: all SourcePackage: alsa-driver
[Desktop-packages] [Bug 1707259] Re: Xorg crashed with SIGABRT in OsAbort()
*** This bug is a duplicate of bug 1546541 *** https://bugs.launchpad.net/bugs/1546541 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg-server (Ubuntu) Status: New => Confirmed -- 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/1707259 Title: Xorg crashed with SIGABRT in OsAbort() Status in xorg-server package in Ubuntu: Confirmed Bug description: Just crashed after logging into unity7. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: xserver-xorg-core 2:1.19.3-1ubuntu2 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 CrashCounter: 1 Date: Fri Jul 28 11:14:47 2017 DistroCodename: artful DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg InstallationDate: Installed on 2017-06-12 (46 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170611) ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch ProcEnviron: PATH=(custom, no user) Signal: 6 SourcePackage: xorg-server StacktraceTop: OsAbort () ?? () FatalError () CreateWellKnownSockets () ?? () Title: Xorg crashed with SIGABRT in OsAbort() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1707259/+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 927952] Re: When I press the Print Screen button, it will not appear in "Save Screenshot" window.
Just recently upgraded to bionic, and after using it for a while I mostly got used to it, but the one feature that keeps bothering me painfully is the lack of the printscreen dialog. I understand the initiative to adopt gnome standards, but this is introducing a big inconvenience in comparison to how it was functional in the Unity desktop. It is not just about being able to save printscreens to an arbitrary location under an arbitrary name. It is even more importantly being able to copy a printscreen into a clipboard without saving it to a file on a disk. I used to be able to just copy a printscreen and Ctrl+V it into a IM window, a email client or any webapp. Now I have to take additional steps to open file manager, navigate to the Pictures folder, locate the one printscreen file I need among other ones, and drag it to where I need it, then, delete it. The functionality and user experience has decreased significantly for me, and on top of that I get constantly annoyed by it. I wish Canonical shipped the previous user experience with the new gnome-desktop based Ubuntu. Even as an opt-in! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screenshot in Ubuntu. https://bugs.launchpad.net/bugs/927952 Title: When I press the Print Screen button, it will not appear in "Save Screenshot" window. Status in Ayatana Design: Fix Released Status in Gnome Screenshot: Expired Status in gnome-screenshot package in Ubuntu: Fix Released Status in gnome-screenshot source package in Precise: Fix Released Status in gnome-screenshot package in Debian: Confirmed Bug description: When taking a screenshot with Print Screen or Alt+Print Screen a dialog box asking you what and where to save the file no longer appears. So while you hear a camera sound you have no other confirmation that a screenshot was really taken. Additionally, there is no way of knowing where the screenshot went. I'd imagine this will be particularly problematic for new users of Ubuntu. ProblemType: BugDistroRelease: Ubuntu 12.04 Package: gnome-screenshot 3.3.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-14.23-generic 3.2.3 Uname: Linux 3.2.0-14-generic x86_64 ApportVersion: 1.91-0ubuntu1 Architecture: amd64 Date: Mon Feb 6 23:54:17 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (2029.1)SourcePackage: gnome-screenshot UpgradeStatus: Upgraded to precise on 2012-01-27 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/927952/+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 1762314] Re: Sound output too low
Identical symptoms, package version, distro version, also ALC298, also tried windows, only difference is computer model (Lenovo T570). Confirmed on two identical computers with identical setups. Sorry, don't know how to generate a new report or add debug info. -- 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/1762314 Title: Sound output too low Status in alsa-driver package in Ubuntu: Confirmed Bug description: Sound output on lenovo p51s is too low. No option to go above 100% in volume settings. Download pulse audio volume control to raise application and output volume to 153%, which helps to some extent, but then leads to distortion. Was running windows 10 on same system and audio was loud enough! Also after this morning s update, the volume keys no longer work, even after re-mapping them in shortcuts.3 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jatin 2098 F pulseaudio CurrentDesktop: Budgie:GNOME Date: Sun Apr 8 22:50:04 2018 InstallationDate: Installed on 2018-03-23 (17 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180307.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: High background noise, or volume is too low Title: [20HCS06601, Realtek ALC298, Speaker, Internal] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/03/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1VET36W (1.26 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HCS06601 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1VET36W(1.26):bd10/03/2017:svnLENOVO:pn20HCS06601:pvrThinkPadP51s:rvnLENOVO:rn20HCS06601:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P51s dmi.product.name: 20HCS06601 dmi.product.version: ThinkPad P51s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1762314/+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 1776125] Re: package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade: triggers looping, abandoned
*** This bug is a duplicate of bug 1770563 *** https://bugs.launchpad.net/bugs/1770563 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1770563, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Tags removed: need-duplicate-check ** This bug has been marked a duplicate of bug 1770563 package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade: triggers looping, abandoned -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-menus in Ubuntu. https://bugs.launchpad.net/bugs/1776125 Title: package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade: triggers looping, abandoned Status in gnome-menus package in Ubuntu: New Bug description: package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade: triggers looping, abandoned ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gnome-menus 3.13.3-11ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Sun Jun 10 19:45:46 2018 Dependencies: DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2017-06-13 (362 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: gnome-menus Title: package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to bionic on 2018-06-11 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-menus/+bug/1776125/+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 1720133] Re: USB 3.0 displays are black on Ubuntu after x.org update to 1.18.3 or newer
Please excuse me if this is not the appropriate place to report this. A heads-up for current versions of xorg-server: there appears to be an additional or separate issue with DisplayLink and xorg-server > 1.19.6. 1.20+ doesn't work at all. A display plugged in prevents logging in, and plugging in kills the session and drops you back to login -- at least on Arch. https://github.com/DisplayLink/evdi/issues/133 ** Bug watch added: github.com/DisplayLink/evdi/issues #133 https://github.com/DisplayLink/evdi/issues/133 -- 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/1720133 Title: USB 3.0 displays are black on Ubuntu after x.org update to 1.18.3 or newer Status in xorg-server package in Ubuntu: Triaged Status in xorg-server source package in Xenial: New Status in xorg-server source package in Zesty: New Status in xorg-server source package in Artful: Triaged Bug description: [Impact] * This impacts all Ubuntu releases which received an update of x.org to 1.18.3 or newer, i.e. Ubuntu 16.04, 16.10, 17.04 & 17.10 * End users are unable to use their USB displays unless they workaround the problem which currently involves disabling pageflip for modesetting in x.org.conf file * The fix which has been submitted to x.org extends blacklisting mechanism so the EVDI kernel module which is essential for DisplayLink USB 3.0 devices to work is correctly recognised by x.org. Then the PRIME sync is disabled in such case; The patch can be found here: https://cgit.freedesktop.org/xorg/xserver/commit/?id=fbd80b2c8ebe9fd41229dc5438524d107c071ff1 [Test Case] 1. On a PC device with Ubuntu install DisplayLink SW for Ubuntu v1.3.54 downloaded from http://www.displaylink.com/downloads/ubuntu. Detailed requirements and instructions can be found here: 2. Plug in a DisplayLink USB 3.0 compatible device, e.g. Dell D3100 docking station 3. Plug in an external monitor (HDMI or DisplayPort) to the docking station Expected result: The external monitor should light up and show the desktop Actual result: The monitor remains black or shows frozen desktop. [Regression Potential] * The patchset extends number of modules for which x.org changes its functionality. It checks if "evdi" string is in the syspath so it is quite unlikely there would be any impact on anything else then USB 3.0 displays which use EVDI module. [Other Info] * The patch has been applied to Ubuntu x.org source code built and tested. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1720133/+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 1776127] [NEW] package nvidia-340 (not installed) failed to install/upgrade: 正试图覆盖 /lib/udev/rules.d/71-nvidia.rules，它同时被包含于软件包 nvidia-kernel-common-396 396.24.02-0ubuntu0~gpu1
Public bug reported: When I try to install nvidia-340, it report an error ProblemType: Package DistroRelease: Ubuntu 18.04 Package: nvidia-340 (not installed) ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 Date: Mon Jun 11 09:03:22 2018 ErrorMessage: 正试图覆盖 /lib/udev/rules.d/71-nvidia.rules，它同时被包含于软件包 nvidia-kernel-common-396 396.24.02-0ubuntu0~gpu18.04.1 InstallationDate: Installed on 2018-05-17 (24 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: nvidia-graphics-drivers-340 Title: package nvidia-340 (not installed) failed to install/upgrade: 正试图覆盖 /lib/udev/rules.d/71-nvidia.rules，它同时被包含于软件包 nvidia-kernel-common-396 396.24.02-0ubuntu0~gpu18.04.1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-340 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1776127 Title: package nvidia-340 (not installed) failed to install/upgrade: 正试图覆盖 /lib/udev/rules.d/71-nvidia.rules，它同时被包含于软件包 nvidia-kernel-common-396 396.24.02-0ubuntu0~gpu18.04.1 Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: When I try to install nvidia-340, it report an error ProblemType: Package DistroRelease: Ubuntu 18.04 Package: nvidia-340 (not installed) ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 Date: Mon Jun 11 09:03:22 2018 ErrorMessage: 正试图覆盖 /lib/udev/rules.d/71-nvidia.rules，它同时被包含于软件包 nvidia-kernel-common-396 396.24.02-0ubuntu0~gpu18.04.1 InstallationDate: Installed on 2018-05-17 (24 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: nvidia-graphics-drivers-340 Title: package nvidia-340 (not installed) failed to install/upgrade: 正试图覆盖 /lib/udev/rules.d/71-nvidia.rules，它同时被包含于软件包 nvidia-kernel-common-396 396.24.02-0ubuntu0~gpu18.04.1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1776127/+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 1762314] Re: Sound output too low
Status changed to 'Confirmed' because the bug affects multiple users. ** 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/1762314 Title: Sound output too low Status in alsa-driver package in Ubuntu: Confirmed Bug description: Sound output on lenovo p51s is too low. No option to go above 100% in volume settings. Download pulse audio volume control to raise application and output volume to 153%, which helps to some extent, but then leads to distortion. Was running windows 10 on same system and audio was loud enough! Also after this morning s update, the volume keys no longer work, even after re-mapping them in shortcuts.3 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jatin 2098 F pulseaudio CurrentDesktop: Budgie:GNOME Date: Sun Apr 8 22:50:04 2018 InstallationDate: Installed on 2018-03-23 (17 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180307.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: High background noise, or volume is too low Title: [20HCS06601, Realtek ALC298, Speaker, Internal] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/03/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1VET36W (1.26 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HCS06601 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1VET36W(1.26):bd10/03/2017:svnLENOVO:pn20HCS06601:pvrThinkPadP51s:rvnLENOVO:rn20HCS06601:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P51s dmi.product.name: 20HCS06601 dmi.product.version: ThinkPad P51s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1762314/+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 1776125] [NEW] package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade: triggers looping, abandoned
*** This bug is a duplicate of bug 1770563 *** https://bugs.launchpad.net/bugs/1770563 Public bug reported: package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade: triggers looping, abandoned ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gnome-menus 3.13.3-11ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Sun Jun 10 19:45:46 2018 Dependencies: DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2017-06-13 (362 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: gnome-menus Title: package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to bionic on 2018-06-11 (0 days ago) ** Affects: gnome-menus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-menus in Ubuntu. https://bugs.launchpad.net/bugs/1776125 Title: package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade: triggers looping, abandoned Status in gnome-menus package in Ubuntu: New Bug description: package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade: triggers looping, abandoned ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gnome-menus 3.13.3-11ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Sun Jun 10 19:45:46 2018 Dependencies: DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2017-06-13 (362 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: gnome-menus Title: package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to bionic on 2018-06-11 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-menus/+bug/1776125/+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 1609750] Re: Audio not working on Acer Chromebook R11
Launchpad has imported 31 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=151521.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.
On 2016-08-05T07:04:52+00:00 timo.jyrinki wrote:
Created attachment 227601
dmesg
It's a Braswell 14nm platform with Coreboot and SeaBIOS as a payload to
boot Ubuntu 16.10 (+ mainline 4.7 kernel). Sound does not work and the
UIs don't show any devices either since pulseaudio fails so start with
"failed to detect any sound hardware".
According to Chromebook community person, there might be some required
initialization missing that the ChromeOS payload ("depthcharge") is
usually responsible for.
alsa-info at: http://www.alsa-
project.org/db/?f=c193a12f53608b68d259f574b4791d18a522a000
dmesg, dmidecode, lshw, lspci as attachments.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1609750/comments/20
On 2016-08-05T07:05:21+00:00 timo.jyrinki wrote:
Created attachment 227611
dmidecode
Reply at:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1609750/comments/21
On 2016-08-05T07:05:44+00:00 timo.jyrinki wrote:
Created attachment 227621
lshw
Reply at:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1609750/comments/22
On 2016-08-05T07:06:03+00:00 timo.jyrinki wrote:
Created attachment 227631
lspci
Reply at:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1609750/comments/23
On 2016-08-08T14:06:46+00:00 timo.jyrinki wrote:
It seems these should get merged?
https://github.com/plbossart/sound/branches/all?query=byt-cht
Reply at:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1609750/comments/24
On 2016-08-09T20:03:04+00:00 tiwai wrote:
The relevant codes have been already merged to upstream recently.
Could you try 4.8-rc1?
Reply at:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1609750/comments/25
On 2016-08-10T13:57:03+00:00 timo.jyrinki wrote:
Created attachment 228161
dmesg 4.8rc1
No change, no sound and cht-bsw-max98090 cht-bsw-max98090:
snd_soc_register_card failed -517
Reply at:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1609750/comments/26
On 2016-08-22T09:49:19+00:00 vinod.koul wrote:
(In reply to Timo Jyrinki from comment #6)
> Created attachment 228161 [details]
> dmesg 4.8rc1
>
> No change, no sound and cht-bsw-max98090 cht-bsw-max98090:
> snd_soc_register_card failed -517
SST driver seems to initialze well. This i2c seems to fail..
[ 19.972195] cht-bsw-max98090 cht-bsw-max98090: ASoC: i2c-104C227E:00 not
registered
[ 19.972207] cht-bsw-max98090 cht-bsw-max98090: snd_soc_register_card failed
-517
I will check the codec on this device, if you know please do let me
know...
Reply at:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1609750/comments/27
On 2016-08-24T08:21:35+00:00 vinod.koul wrote:
okay I checked. With coreboot this seems to work fine.
Cna you check the SeaBIOS used and get it to create the I2C device
104C227E so codec can be loaded thus completing the sound card
Reply at:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1609750/comments/28
On 2016-08-24T09:27:31+00:00 timo.jyrinki wrote:
Thank you, sounds like a very useful bit of information. I've passed on
the info to the G+ coreboot on Chromebooks community where the people
creating the SeaBIOS images are.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1609750/comments/29
On 2016-08-24T10:51:23+00:00 timo.jyrinki wrote:
And copy-pasting here (from
https://plus.google.com/u/0/+TimoJyrinki/posts/R1AqYCSPru8 ):
"SeaBIOS doesn't do hardware initialisation, that's down to coreboot, so
no, I can't. Obviously, the sound hardware works under the ChromeOS
kernel so I would guess they need to figure out what the ChromeOS kernel
is doing that upstream isn't."
Reply at:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1609750/comments/30
On 2016-08-26T09:07:20+00:00 timo.jyrinki
[Desktop-packages] [Bug 1776123] [NEW] usb-modeswitch-dispatcher does not find its data files
Public bug reported: Description:Ubuntu 16.04.4 LTS Release:16.04 Ubuntu 16.04 LTS (Xenial) Package versions: usb-modeswitch: Instalado: 2.2.5+repack0-1ubuntu1 Candidato: 2.2.5+repack0-1ubuntu1 Tabela de versão: *** 2.2.5+repack0-1ubuntu1 500 500 http://br.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status usb-modeswitch-data: Instalado: 20151101-1 Candidato: 20151101-1 Tabela de versão: *** 20151101-1 500 500 http://br.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 500 http://br.archive.ubuntu.com/ubuntu xenial/main i386 Packages 100 /var/lib/dpkg/status Modem used: Huawei E392 (Device ID 0x12d1:0x1505) Description: usb_modeswitch fails and does not add the comms device to /dev. Journalctl log: Jun 10 21:35:27 dell.luzemario.net.br kernel: usb 1-3: new high-speed USB device number 14 using xhci_hcd Jun 10 21:35:27 dell.luzemario.net.br kernel: usb 1-3: New USB device found, idVendor=12d1, idProduct=1505 Jun 10 21:35:27 dell.luzemario.net.br kernel: usb 1-3: New USB device strings: Mfr=3, Product=2, SerialNumber=0 Jun 10 21:35:27 dell.luzemario.net.br kernel: usb 1-3: Product: HUAWEI Mobile Jun 10 21:35:27 dell.luzemario.net.br kernel: usb 1-3: Manufacturer: Huawei Technologies Jun 10 21:35:27 dell.luzemario.net.br mtp-probe[8161]: checking bus 1, device 14: "/sys/devices/pci:00/:00:14.0/usb1/1-3" Jun 10 21:35:27 dell.luzemario.net.br kernel: usb-storage 1-3:1.0: USB Mass Storage device detected Jun 10 21:35:27 dell.luzemario.net.br kernel: scsi host12: usb-storage 1-3:1.0 Jun 10 21:35:27 dell.luzemario.net.br mtp-probe[8161]: bus: 1, device: 14 was not an MTP device Jun 10 21:35:27 dell.luzemario.net.br systemd[1]: Starting USB_ModeSwitch_1-3:1.0... Jun 10 21:35:27 dell.luzemario.net.br usb_modeswitch_dispatcher[8180]: Could not read attribute: No such file or directory Jun 10 21:35:27 dell.luzemario.net.br usb_modeswitch_dispatcher[8180]: Could not read attribute: No such file or directory Jun 10 21:35:27 dell.luzemario.net.br usb_modeswitch_dispatcher[8180]: Could not read attribute: No such file or directory Jun 10 21:35:27 dell.luzemario.net.br usb_modeswitch_dispatcher[8180]: Could not read attribute: No such file or directory Jun 10 21:35:28 dell.luzemario.net.br kernel: scsi 12:0:0:0: CD-ROM HUAWEI Mass Storage 2.31 PQ: 0 ANSI: 0 Jun 10 21:35:28 dell.luzemario.net.br kernel: sr 12:0:0:0: [sr0] scsi-1 drive Jun 10 21:35:28 dell.luzemario.net.br kernel: sr 12:0:0:0: Attached scsi CD-ROM sr0 Jun 10 21:35:28 dell.luzemario.net.br kernel: sr 12:0:0:0: Attached scsi generic sg2 type 5 Jun 10 21:35:28 dell.luzemario.net.br usb_modeswitch[8198]: switch device 12d1:1505 on 001/014 Jun 10 21:35:29 dell.luzemario.net.br usb_modeswitch_dispatcher[8180]: Could not read attribute: No such file or directory Jun 10 21:35:29 dell.luzemario.net.br usb_modeswitch[8180]: usb_modeswitch: switched to 12d1:1505 on 1/14 Jun 10 21:35:30 dell.luzemario.net.br usb_modeswitch_dispatcher[8180]: Unable to open bind list file: No such file or directory Jun 10 21:35:30 dell.luzemario.net.br usb_modeswitch[8180]: usb_modeswitch: add device ID 12d1:1505 to driver option Jun 10 21:35:30 dell.luzemario.net.br usb_modeswitch[8180]: usb_modeswitch: please report the device ID to the Linux USB developers! Jun 10 21:35:30 dell.luzemario.net.br kernel: usb 1-3: USB disconnect, device number 14 Jun 10 21:35:35 dell.luzemario.net.br kernel: usb 1-3: new high-speed USB device number 15 using xhci_hcd Jun 10 21:35:35 dell.luzemario.net.br kernel: usb 1-3: New USB device found, idVendor=12d1, idProduct=1505 Jun 10 21:35:35 dell.luzemario.net.br kernel: usb 1-3: New USB device strings: Mfr=3, Product=2, SerialNumber=0 Jun 10 21:35:35 dell.luzemario.net.br kernel: usb 1-3: Product: HUAWEI Mobile Jun 10 21:35:35 dell.luzemario.net.br kernel: usb 1-3: Manufacturer: Huawei Technologies Jun 10 21:35:35 dell.luzemario.net.br kernel: usb-storage 1-3:1.0: USB Mass Storage device detected Jun 10 21:35:35 dell.luzemario.net.br kernel: scsi host13: usb-storage 1-3:1.0 Jun 10 21:35:35 dell.luzemario.net.br mtp-probe[8214]: checking bus 1, device 15: "/sys/devices/pci:00/:00:14.0/usb1/1-3" Jun 10 21:35:35 dell.luzemario.net.br mtp-probe[8214]: bus: 1, device: 15 was not an MTP device Jun 10 21:35:36 dell.luzemario.net.br kernel: scsi 13:0:0:0: CD-ROM HUAWEI Mass Storage 2.31 PQ: 0 ANSI: 0 Jun 10 21:35:36 dell.luzemario.net.br kernel: sr 13:0:0:0: [sr0] scsi-1 drive Jun 10 21:35:36 dell.luzemario.net.br kernel: sr 13:0:0:0: Attached scsi CD-ROM sr0 Jun 10 21:35:36 dell.luzemario.net.br kernel: sr 13:0:0:0: Attached scsi generic sg2 type 5 Jun 10 21:35:37 dell.luzemario.net.br systemd[1]: Started USB_ModeSwitch_1-3:1.0. ** Affects: usb-modeswitch (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of
[Desktop-packages] [Bug 1012533] Re: No route to VPN server added when connected via Mobile Broadband
Looks like that's still a bug in Xenial… :-(
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-openvpn in Ubuntu.
https://bugs.launchpad.net/bugs/1012533
Title:
No route to VPN server added when connected via Mobile Broadband
Status in network-manager-openvpn package in Ubuntu:
Confirmed
Bug description:
Ubuntu 12.04 LTS
network-manager-openvpn 0.9.4.0-ubuntu1
I'm trying to use OpenVPN via Network Manager in a configuration that passes
all traffic over the VPN tunnel (i.e. the default route is set to tun0).
This works fine when using wifi as the underlying network connection,
but does not work when I use UMTS ("Mobile Broadband") as the
underlying connection. (Both connections work fine for accessing the
Internet without VPN.)
The tunnel is established but no traffic is passed over it, because
the routing table is wrong.
Using OpenVPN over wifi, the routing table looks something like this
after the VPN connection is established:
# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric RefUse Iface
0.0.0.0 10.1.1.53 0.0.0.0 UG0 00 tun0
[...]
10.1.1.53 0.0.0.0 255.255.255.255 UH0 00 tun0
[...]
172.16.250.00.0.0.0 255.255.255.0 U 2 00 wlan0
192.0.2.115 172.16.250.254 255.255.255.255 UGH 0 00 wlan0
169.254.0.0 0.0.0.0 255.255.0.0 U 1000 00 wlan0
[...]
As you can see, there is a host route to the VPN server (192.0.2.115), and a
default route to the tunnel interface. Thus, everything works as expected.
(I have redacted our internal routes that are pushed via OpenVPN and are also
in the routing table, because they are not relevant for this problem.)
Using Mobile Broadband, the routing table looks something like this
(without VPN)
# ifconfig hso0
hso0 Link encap:UNSPEC HWaddr
00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:93.111.28.239 P-t-P:93.111.28.239 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1486 Metric:1
RX packets:437 errors:0 dropped:0 overruns:0 frame:0
TX packets:442 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:10
RX bytes:46787 (46.7 KB) TX bytes:95946 (95.9 KB)
# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric RefUse Iface
0.0.0.0 0.0.0.0 0.0.0.0 U 0 00 hso0
169.254.0.0 0.0.0.0 255.255.0.0 U 1000 00 hso0
After the VPN connection is established, it looks something like this:
# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric RefUse Iface
0.0.0.0 10.222.193.53 0.0.0.0 UG0 00 tun0
[...]
10.222.193.53 0.0.0.0 255.255.255.255 UH0 00 tun0
169.254.0.0 0.0.0.0 255.255.0.0 U 1000 00 hso0
[...]
There is a default route to the tunnel interface, but no host route to
the VPN server. Therefor, the VPN-encapsulated datagrams are sent to
the VPN interface once again, which clearly is not right.
Why does Network Manager not add the host route like it does when
connected over wifi? Is it because hso0 is a P-t-P link?
To work around this, I currently run
# ip route add 192.0.2.115/32 dev hso0
which solves the problem, but it's annoying to have to do this by hand
every time.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1012533/+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 1774201] Re: package libfreerdp-client2-2 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libfreerdp-client2.so.2.0.0', which is also
I've installed freerdp2 via remmina-ppa and running Ubuntu Cosmic and this is the console log: sm4rk0@Aspire-5336:~$ sudo apt --fix-broken install [sudo] password for sm4rk0: Reading package lists... Done Building dependency tree Reading state information... Done Correcting dependencies... Done The following additional packages will be installed: libfreerdp-client2-2 libfreerdp2-2 libwinpr2-2 The following NEW packages will be installed: libfreerdp-client2-2 libfreerdp2-2 libwinpr2-2 0 upgraded, 3 newly installed, 0 to remove and 41 not upgraded. 1 not fully installed or removed. Need to get 0 B/1032 kB of archives. After this operation, 3425 kB of additional disk space will be used. Do you want to continue? [Y/n] y (Reading database ... 312212 files and directories currently installed.) Preparing to unpack .../libwinpr2-2_2.0.0~git201805301039-0+remmina201805311850.r73588bc.def0b2dc~ubuntu18.10.1_amd64.deb ... Unpacking libwinpr2-2:amd64 (2.0.0~git201805301039-0+remmina201805311850.r73588bc.def0b2dc~ubuntu18.10.1) ... dpkg: error processing archive /var/cache/apt/archives/libwinpr2-2_2.0.0~git201805301039-0+remmina201805311850.r73588bc.def0b2dc~ubuntu18.10.1_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libwinpr2.so.2.0.0', which is also in package libwinpr2:amd64 2.0.0~git201804050820-0+remmina201804082000.ra9ecd6a.d29dd283~ubuntu18.04.1 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Preparing to unpack .../libfreerdp2-2_2.0.0~git201805301039-0+remmina201805311850.r73588bc.def0b2dc~ubuntu18.10.1_amd64.deb ... Unpacking libfreerdp2-2:amd64 (2.0.0~git201805301039-0+remmina201805311850.r73588bc.def0b2dc~ubuntu18.10.1) ... dpkg: error processing archive /var/cache/apt/archives/libfreerdp2-2_2.0.0~git201805301039-0+remmina201805311850.r73588bc.def0b2dc~ubuntu18.10.1_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libfreerdp2.so.2.0.0', which is also in package libfreerdp2:amd64 2.0.0~git201804050820-0+remmina201804082000.ra9ecd6a.d29dd283~ubuntu18.04.1 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Preparing to unpack .../libfreerdp-client2-2_2.0.0~git201805301039-0+remmina201805311850.r73588bc.def0b2dc~ubuntu18.10.1_amd64.deb ... Unpacking libfreerdp-client2-2:amd64 (2.0.0~git201805301039-0+remmina201805311850.r73588bc.def0b2dc~ubuntu18.10.1) ... dpkg: error processing archive /var/cache/apt/archives/libfreerdp-client2-2_2.0.0~git201805301039-0+remmina201805311850.r73588bc.def0b2dc~ubuntu18.10.1_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libfreerdp-client2.so.2.0.0', which is also in package libfreerdp-client2:amd64 2.0.0~git201804050820-0+remmina201804082000.ra9ecd6a.d29dd283~ubuntu18.04.1 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/libwinpr2-2_2.0.0~git201805301039-0+remmina201805311850.r73588bc.def0b2dc~ubuntu18.10.1_amd64.deb /var/cache/apt/archives/libfreerdp2-2_2.0.0~git201805301039-0+remmina201805311850.r73588bc.def0b2dc~ubuntu18.10.1_amd64.deb /var/cache/apt/archives/libfreerdp-client2-2_2.0.0~git201805301039-0+remmina201805311850.r73588bc.def0b2dc~ubuntu18.10.1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to freerdp2 in Ubuntu. https://bugs.launchpad.net/bugs/1774201 Title: package libfreerdp-client2-2 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu /libfreerdp-client2.so.2.0.0', which is also in package libfreerdp- client2:amd64 2.0.0~git201804050820-0+remmina201804082000.ra9ecd6a.d29dd283~ubuntu18.04.1 Status in freerdp2 package in Ubuntu: Confirmed Bug description: This error occurs after an update of remmina on
[Desktop-packages] [Bug 508618] Re: Setting max-specpdl-size of 34295 allows segfaults with 'simple' elisp
** Tags added: cosmic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to emacs24 in Ubuntu. https://bugs.launchpad.net/bugs/508618 Title: Setting max-specpdl-size of 34295 allows segfaults with 'simple' elisp Status in emacs23 package in Ubuntu: New Status in emacs24 package in Ubuntu: New Status in emacs25 package in Ubuntu: New Status in emacs25 package in Debian: New Bug description: Binary package hint: emacs23 Setting max-specpdl-size higher than 34295, and then running the following code results in a segfault of emacs. I am running a system of mostly 9.04 with some packages (such as this one) upgraded. I know it's kind of pushing emacs to the limit, but still; this seems like an arbitrary limit on emacs' otherwise diety-like functionality. What should happen is emacs should continue to fail to execute with "file-truename: Variable binding depth exceeds max-specpdl-size" as it does below 34295., or at the very least when setting max-specpdl-size higher than 34295 it should warn you that you are making some kind of error if this is not acceptable. example code: (defun por (pcurrent pb numberleft) (if (= numberleft 0) pcurrent (por (- (+ pcurrent pb) (* pcurrent pb)) pb (- numberleft 1 (por 0 0.01 1) (setq max-lisp-eval-depth 100) ; this may be necessary, but doesn't appear to be the problem (setq max-specpdl-size 34295) ; setting this lower results in predictable, expected behaviour - emacs refuses to run the result, citing max-specpdl-size not high enough. Setting this higher (like...34296), results in a segfault of emacs emacs23: Installé : 23.1+1-4ubuntu3 Candidat : 23.1+1-4ubuntu3 Table de version : *** 23.1+1-4ubuntu3 0 100 /var/lib/dpkg/status ProblemType: Bug Architecture: amd64 DistroRelease: Ubuntu 9.04 Package: emacs23 23.1+1-4ubuntu3 ProcEnviron: PATH=(custom, user) LANG=fr_CA.UTF-8 SHELL=/bin/bash SourcePackage: emacs23 Uname: Linux 2.6.28-16-generic x86_64 UnreportableReason: Ceci n'est pas un authentique paquet Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/emacs23/+bug/508618/+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 1774201] Re: package libfreerdp-client2-2 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libfreerdp-client2.so.2.0.0', which is also
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: freerdp2 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to freerdp2 in Ubuntu. https://bugs.launchpad.net/bugs/1774201 Title: package libfreerdp-client2-2 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu /libfreerdp-client2.so.2.0.0', which is also in package libfreerdp- client2:amd64 2.0.0~git201804050820-0+remmina201804082000.ra9ecd6a.d29dd283~ubuntu18.04.1 Status in freerdp2 package in Ubuntu: Confirmed Bug description: This error occurs after an update of remmina on yesterday ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libfreerdp-client2-2 (not installed) ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Wed May 30 10:07:21 2018 ErrorMessage: trying to overwrite '/usr/lib/x86_64-linux-gnu/libfreerdp-client2.so.2.0.0', which is also in package libfreerdp-client2:amd64 2.0.0~git201804050820-0+remmina201804082000.ra9ecd6a.d29dd283~ubuntu18.04.1 InstallationDate: Installed on 2018-05-23 (7 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: freerdp2 Title: package libfreerdp-client2-2 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libfreerdp-client2.so.2.0.0', which is also in package libfreerdp-client2:amd64 2.0.0~git201804050820-0+remmina201804082000.ra9ecd6a.d29dd283~ubuntu18.04.1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freerdp2/+bug/1774201/+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 1761554] Re: [bionic] Extended characters in GNOME screen keyboard don't get entered
This bug was fixed in the package im-config - 0.34-1ubuntu3 --- im-config (0.34-1ubuntu3) cosmic; urgency=medium * debian/patches/dont-set-GTK_IM_MODULE-on-wayland.patch: - Dropped. The 0.34-1ubuntu2 changes reversed due to regression, e.g. LibreOffice crash when using IBus (LP: #1761554). -- Gunnar Hjalmarsson Sun, 10 Jun 2018 21:55:00 +0200 ** Changed in: im-config (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to im-config in Ubuntu. https://bugs.launchpad.net/bugs/1761554 Title: [bionic] Extended characters in GNOME screen keyboard don't get entered Status in gnome-shell package in Ubuntu: Triaged Status in gnome-user-docs package in Ubuntu: New Status in im-config package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: Triaged Status in gnome-user-docs source package in Bionic: New Status in im-config source package in Bionic: In Progress Bug description: im-config SRU request = [Impact] When in a Wayland session, accented characters as well as some special characters can't be entered via the screen keyboard. The issue is fixed via the proposed upload of im-config, which has been changed to not set the GTK_IM_MODULE environment variable for IBus on Wayland (previously GTK_IM_MODULE was set to "ibus"). Making this accessibility tool work without issues on Wayland is important enough to justify this SRU. [Test Case] 1. Log in to an Ubuntu on Wayland session 2. Open gedit and enable the screen keyboard (Settings -> Universal Access -> Typing) -> Accented characters via long-press does not work. Example: long-press a and select à from the popup Also, certain keys for special characters result in incorrect characters or nothing. Examples: ~, √, ÷, ×, <, >, ¢ 3. Install im-config from bionic-proposed 4. Relogin and repeat step 2. -> Everything works as expected [Regression Potential] There are reasons to presuppose that GTK_IM_MODULE does not need to be set at all for IBus on a GNOME desktop: * GTK has a mechanism for selecting a built-in IM. * IBus is default in GNOME, and vanilla GNOME (which does not make use of im-config) does not set the GTK_IM_MODULE environment variable. But the change is only made for Wayland sessions, which is not default in 18.04. Given this limitation, the regression risk is deemed to be low. [Original description] I filed this bug upstream last month but it hasn't gotten much attention so I'm filing it here because I think we need to track this issue for the Ubuntu 18.04 release https://gitlab.gnome.org/GNOME/gnome-shell/issues/109 Test Case - 1. Open the Settings app. Click Universal Access. 2. Enable the Screen Keyboard. (Optionally, turn on "Always Show Universal Access Menu" to make turning the Screen Keyboard on and off easier.) 3. Open Text Editor 4. Click the u button on the Screen Keyboard 5. Long-press the u button on the Screen Keyboard for a few seconds. On the popup, click the ü character. What Happens In Step 4, u is entered in the Text Editor document. Nothing is entered in Step 5. This bug affects any of the "extended characters" clicked on from the long-press popup in the Screen Keyboard. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1761554/+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 1761554] Re: [bionic] Extended characters in GNOME screen keyboard don't get entered
** Changed in: im-config (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to im-config in Ubuntu. https://bugs.launchpad.net/bugs/1761554 Title: [bionic] Extended characters in GNOME screen keyboard don't get entered Status in gnome-shell package in Ubuntu: Triaged Status in gnome-user-docs package in Ubuntu: New Status in im-config package in Ubuntu: Fix Committed Status in gnome-shell source package in Bionic: Triaged Status in gnome-user-docs source package in Bionic: New Status in im-config source package in Bionic: In Progress Bug description: im-config SRU request = [Impact] When in a Wayland session, accented characters as well as some special characters can't be entered via the screen keyboard. The issue is fixed via the proposed upload of im-config, which has been changed to not set the GTK_IM_MODULE environment variable for IBus on Wayland (previously GTK_IM_MODULE was set to "ibus"). Making this accessibility tool work without issues on Wayland is important enough to justify this SRU. [Test Case] 1. Log in to an Ubuntu on Wayland session 2. Open gedit and enable the screen keyboard (Settings -> Universal Access -> Typing) -> Accented characters via long-press does not work. Example: long-press a and select à from the popup Also, certain keys for special characters result in incorrect characters or nothing. Examples: ~, √, ÷, ×, <, >, ¢ 3. Install im-config from bionic-proposed 4. Relogin and repeat step 2. -> Everything works as expected [Regression Potential] There are reasons to presuppose that GTK_IM_MODULE does not need to be set at all for IBus on a GNOME desktop: * GTK has a mechanism for selecting a built-in IM. * IBus is default in GNOME, and vanilla GNOME (which does not make use of im-config) does not set the GTK_IM_MODULE environment variable. But the change is only made for Wayland sessions, which is not default in 18.04. Given this limitation, the regression risk is deemed to be low. [Original description] I filed this bug upstream last month but it hasn't gotten much attention so I'm filing it here because I think we need to track this issue for the Ubuntu 18.04 release https://gitlab.gnome.org/GNOME/gnome-shell/issues/109 Test Case - 1. Open the Settings app. Click Universal Access. 2. Enable the Screen Keyboard. (Optionally, turn on "Always Show Universal Access Menu" to make turning the Screen Keyboard on and off easier.) 3. Open Text Editor 4. Click the u button on the Screen Keyboard 5. Long-press the u button on the Screen Keyboard for a few seconds. On the popup, click the ü character. What Happens In Step 4, u is entered in the Text Editor document. Nothing is entered in Step 5. This bug affects any of the "extended characters" clicked on from the long-press popup in the Screen Keyboard. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1761554/+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 1769501] Re: /usr/lib/cups/filter/hpcups assertion failure when plugging in a HP LaserJet M1132 MFP printer/scanner
Hi srinivas, On 6 June 2018 at 13:37, srinivas <1769...@bugs.launchpad.net> wrote: > Did you install hplip-3.18.4-plugin.run? > hplip-3.18.4-plugin.run is required for the scan to work. > Yes, I did. I reinstalled Ubuntu 18.04 and ran hplip-3.18.4-plugin.run As is my wont, I took screenshots during the process and saved the logfiles. I have attached those files to this message. I did some detective work regarding the error message "Gtk-Message Failed to load module canberra-gtk-module". It can be apparently fixed by installing the package libcanberra-gtk-module It _might_ be a good idea to add libcanberra-gtk-module to the list of package dependencies. That might clear up one problem. I am still learning Python and, as I learn more, I'll be better equipped to try and help solve these problems. BW, Ian -- -- ACCU - Professionalism in programming - http://www.accu.org -- My writing - https://sites.google.com/site/ianbruntlett/ -- Free Software page - https://sites.google.com/site/ianbruntlett/home/free-software ** Attachment added: "5-looking-for-references-to-canberra.png" https://bugs.launchpad.net/bugs/1769501/+attachment/5151002/+files/5-looking-for-references-to-canberra.png ** Attachment added: "4-searching-for-canberra-gtk-module.png" https://bugs.launchpad.net/bugs/1769501/+attachment/5151003/+files/4-searching-for-canberra-gtk-module.png ** Attachment added: "3-hp-scan-from-command-line-fails.png" https://bugs.launchpad.net/bugs/1769501/+attachment/5151004/+files/3-hp-scan-from-command-line-fails.png ** Attachment added: "2-failure-to-scan.png" https://bugs.launchpad.net/bugs/1769501/+attachment/5151005/+files/2-failure-to-scan.png ** Attachment added: "1-no-system-tray-detected.png" https://bugs.launchpad.net/bugs/1769501/+attachment/5151006/+files/1-no-system-tray-detected.png ** Attachment added: "hplip-install_Sun-10-Jun-2018_18:24:21.log" https://bugs.launchpad.net/bugs/1769501/+attachment/5151007/+files/hplip-install_Sun-10-Jun-2018_18%3A24%3A21.log ** Attachment added: "config.log" https://bugs.launchpad.net/bugs/1769501/+attachment/5151008/+files/config.log -- 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/1769501 Title: /usr/lib/cups/filter/hpcups assertion failure when plugging in a HP LaserJet M1132 MFP printer/scanner Status in HPLIP: In Progress Status in hplip package in Ubuntu: In Progress Bug description: Installed Ubuntu 18.04 64-bit on lenovo ThinkPad T420 (hostname: newton). Intel i5-2520m 2.5GHz 64-bit CPU, 8GiB RAM, 298GiB hard drive, DVD writer, Ethernet and WiFi connections. Attached my LaserJet, Ubuntu ran some software to install the printer (probably trying to run the HP software) and /usr/lib/cups/filter/hpcups crashed with the assertion failure: free(): invalid pointer. Rebooted, installed package hplip-gui, ran sudo hp-setup – it needed to ask me (the user) some questions. That kept it happy and it ran successfully. I ended up with two similarly named HP Printers. Printed to the right one and it worked. Renamed the other one to avoid confusion whilst printing. To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/1769501/+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 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)
Release package is already unstable and isn't able to it's job. I don't see any reasons not to deploy this excepting bureaucracy. -- 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/1766137 Title: [regression] Password accepted but login fails (blank purple screen and mouse pointer only) Status in gdm: Fix Released Status in Release Notes for Ubuntu: Fix Released Status in gdm3 package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Invalid Status in gdm3 source package in Bionic: Fix Committed Status in gnome-shell source package in Bionic: Invalid Bug description: [ Description ] Due to a refcounting bug, a GDBusConnection was getting disposed when it was still required. The symptom of this was that you couldn't log in on the second attempt if you'd got your password wrong on the first attempt. All you'd see is a blank purple screen and mouse pointer only. [ Test case ] 1. Boot to GDM 2. Click your username 3. Type the wrong password a couple of times, pressing enter after each time 4. Type the right password If the bug is happening, after 4. the system hangs at a blank screen with the mouse cursor. If you then switch to a VT or otherwise connect to the machine, you can examine the journal and you'll see a G_IS_DBUS_CONNECTION failure. [ Fix ] Marco and I worked upstream on this fix. We found out that there was a problem like this- The GdmClient has a shared GDBusConnection for its operations. The first time someone calls for it, it is created and stored in the object's private structure. Subsequent calls return *a new reference* to this same object. It turned out that the asynchronous method to get the connection was accidentally unreferencing its object before giving it to the caller if it was returning an already-existing connection. For this to work properly, we need to nullify the pointer we stored when the connection goes away, so we know when to make a new one. There were some cases where we didn't add the weak references required to do that. Those are also fixed. [ Regression potential ] Now we share connections more than we did before. We also more carefully track when to clear our object. If we got this wrong, we might end up leaking the connection or dropping it in even more cases. [ Original report ] WORKAROUND: After typing an incorrect password, click Cancel, then click your name, then enter your password again. --- Trying to log into my session (Gnome, Xorg), if I enter the wrong password before entering it correctly, the session doesn't load and I get a purple screen, a mouse cursor, and an invisible but clickable menu in the top right. If I enter it correctly the first time, there is no problem. I've replicated this from a fresh boot, after logging out and after 'sudo service gdm restart' from the Ctrl-Alt-F4 console. This is a fresh install, and didn't occur when I was using a previous install of 18.04 (until Friday). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 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: ubuntu:GNOME Date: Sun Apr 22 20:31:13 2018 InstallationDate: Installed on 2018-04-22 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180421.1) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1766137/+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 1773561] Re: Xenial/16.04: GIMP needs a security update - unfixed issues (CVE-2017: 17784-17789).
** Information type changed from Public to Public Security
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gimp in Ubuntu.
https://bugs.launchpad.net/bugs/1773561
Title:
Xenial/16.04: GIMP needs a security update - unfixed issues (CVE-2017:
17784-17789).
Status in gimp package in Ubuntu:
Confirmed
Bug description:
Hello.
GIMP package ('Universe/Security' section), available in
"Xenial"/16.04 LTS Release, contains unfixed security issues and is
vulnerable to, for example, heap-buffer over-read, out of bounds read
and stack-based buffer over-read etc. The whole thing is pretty
strange, because Ubuntu Releases released before and after "Xenial",
contains updated GIMP package!
Anyway, it looks this way: in "Trusty" the available version is:
'2.8.10-0ubuntu1.2' (please see [1]). "Bionic" has '2.8.20-1.1'
version (please see [2]). Both Releases contains fixes for mentioned
security issues: CVE-2017-* etc. However, GIMP version in "Xenial" is
'2.8.16-1ubuntu1.1' and does not contain any security updates from
2017. (The last one is from Thu, 30 Jun 2016.; please see [3]).
Security updates with fixes for mentioned CVE's (please compare
changes in 1. and 2. with 3.) were released on Thu., 18 Jan 2018 - for
"Trusty" and Tue., 26 Dec 2017 - for "Bionic". In "Xenial", the last
security update is from Thu., 30 Jun 2016 (fix for CVE-2016-4994) and
there is no further updates!
Here is a CVE list of security issues not fixed in "Xenial", but in
"Trusty" and "Bionic" etc.:
1/ CVE-2017-17784: Heap-buffer over-read in load_image file-gbr.c
2/ CVE-2017-17785: Heap-based buffer overflow in fli_read_brun function
3/ CVE-2017-17786: Out of bounds read
4/ CVE-2017-17787: Heap-based buffer over-read in read_creator_block
5/ CVE-2017-17788: Stack-based buffer over-read in xcf_load_stream
6/ CVE-2017-17789: Heap-based buffer overflow in read_channel_data
And the most important thing: if User had installed GIMP package in
"Xenial" Release, he is affected - since one year, at least - because
of a vulnerable version. Security issues, mentioned above, are from
2017. So, maybe it's a good opportunity to update GIMP to v2.10.2
version, released on 20., May 2018? (Version 2.8.X is very outdated).
I wanted to send an email to Mr Marc Deslauriers, because he made the
last security update for GIMP in "Xenial" (fix for CVE-2016-4994). But
I decided to report a bug on Launchpad. I hope that it's an acceptable
way. If not, I'm sorry.
By the way: similar problems with unfixed security issues, can be
found e.g. in Audacious and Parole packages. But that's a different
story, completely different story...
Thanks, best regards.
__
1.
http://changelogs.ubuntu.com/changelogs/pool/main/g/gimp/gimp_2.8.10-0ubuntu1.2/changelog
2.
http://changelogs.ubuntu.com/changelogs/pool/universe/g/gimp/gimp_2.8.20-2/changelog
3.
http://changelogs.ubuntu.com/changelogs/pool/universe/g/gimp/gimp_2.8.16-1ubuntu1.1/changelog
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1773561/+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 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)
3.28.2-0ubuntu1.1 did work fine for login logout to another user (critical in our environment). It has been few days since it was supposed to be coming and I figured that it is safe now to start installing 18.04, but fresh install 18.04 and I am still getting 3.28.0-Oubuntu1 - will not work. su 10. kesäk. 2018 klo 17.25 OliFre (1766...@bugs.launchpad.net) kirjoitti: > @Ads2 Thanks for the link. Sadly, gdm3 is neither in the > autopkgtest-list, nor update-excuses, nor update-list, so it seems > things are stuck at an earlier stage and the documentation does not > clarify where to find out at which point help could be needed. > > My intention was not to spam this report, but to find out where things are > stuck (it's not obvious) and how to give support. > It's also not about my personal (im)patience, but we have >200 desktops > and >2000 Ubuntu containers and have had to stop the migration after the > first 10 desktops due to this bug (and three(!) other ones which all have > been known *before* release and should either have been release blockers or > been mentioned as "Known Issues" with the new LTS to prevent people from > hopping onto the new supposedly-stable). For the other critical issues, QA > apparently was even worse, since Debian and in one case also RHEL have > already released fixes months or even a year ago, and there has been no > reaction on Launchpad whatsoever yet. Since we are also still affected by > critical bugs in 16.04 which have been open since 16.04's release and could > only be solved by PPA (broken OpenAFS), this makes me wonder whether Ubuntu > still is a valid choice for institutional use, but this discussion > certainly goes off topic here. > > Just let us know if there is something people could help with (testing > etc.). As it stands, the status is completely unclear apart from the > statement _to be patient_ - without indicating what the actual point is > where things are stuck. > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1768619). > https://bugs.launchpad.net/bugs/1766137 > > Title: > [regression] Password accepted but login fails (blank purple screen > and mouse pointer only) > > Status in gdm: > Fix Released > Status in Release Notes for Ubuntu: > Fix Released > Status in gdm3 package in Ubuntu: > Fix Released > Status in gnome-shell package in Ubuntu: > Invalid > Status in gdm3 source package in Bionic: > Fix Committed > Status in gnome-shell source package in Bionic: > Invalid > > Bug description: > [ Description ] > > Due to a refcounting bug, a GDBusConnection was getting disposed when > it was still required. The symptom of this was that you couldn't log > in on the second attempt if you'd got your password wrong on the first > attempt. All you'd see is a blank purple screen and mouse pointer > only. > > [ Test case ] > > 1. Boot to GDM > 2. Click your username > 3. Type the wrong password a couple of times, pressing enter after each > time > 4. Type the right password > > If the bug is happening, after 4. the system hangs at a blank screen > with the mouse cursor. If you then switch to a VT or otherwise connect > to the machine, you can examine the journal and you'll see a > G_IS_DBUS_CONNECTION failure. > > [ Fix ] > > Marco and I worked upstream on this fix. We found out that there was a > problem like this- > > The GdmClient has a shared GDBusConnection for its operations. The > first time someone calls for it, it is created and stored in the > object's private structure. Subsequent calls return *a new reference* > to this same object. It turned out that the asynchronous method to get > the connection was accidentally unreferencing its object before giving > it to the caller if it was returning an already-existing connection. > > For this to work properly, we need to nullify the pointer we stored > when the connection goes away, so we know when to make a new one. > There were some cases where we didn't add the weak references required > to do that. Those are also fixed. > > [ Regression potential ] > > Now we share connections more than we did before. We also more > carefully track when to clear our object. If we got this wrong, we > might end up leaking the connection or dropping it in even more cases. > > [ Original report ] > > WORKAROUND: After typing an incorrect password, click Cancel, then > click your name, then enter your password again. > > --- > > Trying to log into my session (Gnome, Xorg), if I enter the wrong > password before entering it correctly, the session doesn't load and I > get a purple screen, a mouse cursor, and an invisible but clickable > menu in the top right. If I enter it correctly the first time, there > is no problem. > > I've replicated this from a fresh boot, after logging out and after > 'sudo service gdm restart' from the Ctrl-Alt-F4 console. > > This is a fresh
[Desktop-packages] [Bug 1771749] Re: Ethernet connection lost after few minutes since starting
I don't know which kernel version I did use in Xenial (initially I used the normal one, the kernel installed by default, but then I installed UKUU so couldn't remember, but I never had this problem with previous versions of Kubuntu nor any other flavor of Ubuntu nor in any Linux distro, for the case. -- 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/1771749 Title: Ethernet connection lost after few minutes since starting Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: This is the same bug I notified at Bug #1770848 but with a more precise selection of (what I think it is) the package affected and a better description. I made a few days ago a fresh install of the Kubuntu 18.04 LTS and it is most everything Ok, but -I think that- the network-manager has a problem. In the last LTS version, Kubuntu 16.04, nor in any Linux version if I remember well, I never lost connection through Ethernet (the only Internet connection with our desktop PC), but the Bionic Beaver loses the connection every now and then, perhaps within few minutes or hours, but several times per day. When the connection is lost, I note that it disappears any info even mention to any network into the network window and the network manager icon becomes red color. Not matter if I unplug and then plug the ethernet cable again, the ethernet connection is not longer detected and only restarting the PC makes the connection to work again. Incidentally, I also have noticed with this version of Kubuntu 18.04 that in my laptop there is also now a similar problem with the scanner: If I plug it in some USB port of the laptop once Kubuntu 18.04 is already running, it's not detected by Xsane. I have to plug it in before than pressing the power button or at the time of starting the OS, for the scanner to be detected by the scanning program (and then only works with Xsane, not if I use Simple Scan or Skanlite, even when it works under Xsane), as I said in the Bug #1771525 and, evenly, if I unplug the scanner cable from the USB port it is not detected anymore when plugging it again, and only restarting the laptop makes it to be detected. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: KDE Date: Thu May 17 08:24:23 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-05-11 (5 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IpRoute: default via 192.168.1.1 dev enp0s7 proto static metric 100 169.254.0.0/16 dev enp0s7 scope link metric 1000 192.168.1.0/24 dev enp0s7 proto kernel scope link src 192.168.1.3 metric 100 IwConfig: enp0s7no wireless extensions. lono wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true PciNetwork: RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE Conexión cableada 1 1cc37db8-0db8-3887-acf2-59fbbcd0cb1c ethernet 1526538083 jue 17 may 2018 08:21:23 CEST yes 4294967196 no/org/freedesktop/NetworkManager/Settings/1 yes enp0s7 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH enp0s7 ethernet connected /org/freedesktop/NetworkManager/Devices/2 Conexión cableada 1 1cc37db8-0db8-3887-acf2-59fbbcd0cb1c /org/freedesktop/NetworkManager/ActiveConnection/1 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nosotros 1116 F pulseaudio /dev/snd/controlC1:
[Desktop-packages] [Bug 1710858] Re: totem crashed with SIGSEGV in in __GI_____strtoul_l_internal() from __GI___strtoul_l() from g_ascii_strtoull() from _cogl_gpu_info_parse_version_string() from chec
** Changed in: totem (Debian) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1710858 Title: totem crashed with SIGSEGV in in __GI_strtoul_l_internal() from __GI___strtoul_l() from g_ascii_strtoull() from _cogl_gpu_info_parse_version_string() from check_mesa_driver_package() Status in totem package in Ubuntu: Confirmed Status in totem package in Debian: Fix Released Bug description: https://errors.ubuntu.com/problem/8c8cfc48195ee610b89b3b2fa352c622b507d073 --- crashed trying to open .avi video ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: totem 3.25.90.1-0ubuntu1 Uname: Linux 4.12.6-041206-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME Date: Tue Aug 15 12:20:00 2017 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2016-05-20 (451 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcCmdline: /usr/bin/totem --gapplication-service ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash PATH=(custom, no user) LANG=it_IT.UTF-8 SegvAnalysis: Segfault happened at: 0x7fe5160f1bf5 <__GI_strtoul_l_internal+53>: movsbq (%r14),%rax PC (0x7fe5160f1bf5) ok source "(%r14)" (0x) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: totem StacktraceTop: __GI_strtoul_l_internal (nptr=0x0, endptr=0x7fff97eb9aa8, base=10, group=, loc=0x7fe516474820 <_nl_C_locobj>) at ../stdlib/strtol_l.c:293 () at /usr/lib/x86_64-linux-gnu/libcogl.so.20 () at /usr/lib/x86_64-linux-gnu/libcogl.so.20 () at /usr/lib/x86_64-linux-gnu/libcogl.so.20 () at /usr/lib/x86_64-linux-gnu/libcogl.so.20 Title: totem crashed with SIGSEGV in __GI_strtoul_l_internal() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm autopilot cdrom colord dialout dip libvirt libvirtd lpadmin netdev pico plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1710858/+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 1761844] Re: Very large emojis displayed in subject line and in the email list
I tested some solutions found on launchpad and google. with fonts-symbola - but they are without colors. lastly I installed as wrote before (in bug #1644021) Twitter Color Emoji SVGinOT Font: https://github.com/eosrei/twemoji-color-font sudo apt-add-repository ppa:eosrei/fonts sudo apt update sudo apt install fonts-twemoji-svginot This resolved problem with big images of emoji and keep them in color. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1761844 Title: Very large emojis displayed in subject line and in the email list Status in Mozilla Thunderbird: Invalid Status in thunderbird package in Ubuntu: Confirmed Bug description: The list of emails received from Thunderbird shows emojis. This does not happen with all accounts. It appears to be with the last email address added. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: thunderbird 1:52.6.0+build1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia AddonCompatCheckDisabled: False ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: diego 1607 F...m pulseaudio /dev/snd/controlC0: diego 1607 F pulseaudio /dev/snd/controlC1: diego 1607 F pulseaudio BuildID: 20180131200234 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Fri Apr 6 15:58:17 2018 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2018-04-05 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) IpRoute: default via 181.31.1.1 dev enp2s0 proto dhcp metric 100 169.254.0.0/16 dev enp2s0 scope link metric 1000 181.31.1.0/24 dev enp2s0 proto kernel scope link src 181.31.1.84 metric 100 IwConfig: lono wireless extensions. enp2s0no wireless extensions. Locales: extensions.sqlite corrupt or missing PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=52.6.0/20180131200234 (In use) RfKill: RunningIncompatibleAddons: False SourcePackage: thunderbird Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/14/2012 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F4 dmi.board.name: GA-78LMT-S2 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd08/14/2012:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-S2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-S2:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-78LMT-S2 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1761844/+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 1776075] Re: Bluetooth Problem
** Package changed: xorg (Ubuntu) => bluez (Ubuntu) -- 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/1776075 Title: Bluetooth Problem Status in bluez package in Ubuntu: New Bug description: Ich kann Bluetooth nicht Aktivieren ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128 Uname: Linux 4.4.0-127-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sun Jun 10 14:59:59 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7400G] [1002:9994] (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd Trinity [Radeon HD 7400G] [144d:c660] InstallationDate: Installed on 2015-11-17 (935 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: SAMSUNG ELECTRONICS CO., LTD. 535U3C ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-127-generic.efi.signed root=UUID=5b7ab83e-d739-434f-afc7-78ed793a51a1 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/25/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P04RAS.W68.121025.LEO dmi.board.asset.tag: No Asset Tag dmi.board.name: NP535U3C-A03DE dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SEC_SW_REVISION_1234567890ABCD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP04RAS.W68.121025.LEO:bd10/25/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn535U3C:pvrP04RAS:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP535U3C-A03DE:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.name: 535U3C dmi.product.version: P04RAS dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sun Jun 10 14:07:04 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.7 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1776075/+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 1616148] Re: package python-gi 3.20.0-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 101
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pygobject (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pygobject in Ubuntu. https://bugs.launchpad.net/bugs/1616148 Title: package python-gi 3.20.0-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 101 Status in pygobject package in Ubuntu: Confirmed Bug description: No way to install the package python-gi 3.20.0-0ubuntu1 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python-gi 3.20.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic i686 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: i386 Date: Tue Aug 23 16:53:08 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 101 InstallationDate: Installed on 2016-04-02 (143 days ago) InstallationMedia: Lubuntu 14.04.2 LTS "Trusty Tahr" - Release i386 (20150218.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: pygobject Title: package python-gi 3.20.0-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 101 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pygobject/+bug/1616148/+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 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)
@Ads2 Thanks for the link. Sadly, gdm3 is neither in the autopkgtest-list, nor update-excuses, nor update-list, so it seems things are stuck at an earlier stage and the documentation does not clarify where to find out at which point help could be needed. My intention was not to spam this report, but to find out where things are stuck (it's not obvious) and how to give support. It's also not about my personal (im)patience, but we have >200 desktops and >2000 Ubuntu containers and have had to stop the migration after the first 10 desktops due to this bug (and three(!) other ones which all have been known *before* release and should either have been release blockers or been mentioned as "Known Issues" with the new LTS to prevent people from hopping onto the new supposedly-stable). For the other critical issues, QA apparently was even worse, since Debian and in one case also RHEL have already released fixes months or even a year ago, and there has been no reaction on Launchpad whatsoever yet. Since we are also still affected by critical bugs in 16.04 which have been open since 16.04's release and could only be solved by PPA (broken OpenAFS), this makes me wonder whether Ubuntu still is a valid choice for institutional use, but this discussion certainly goes off topic here. Just let us know if there is something people could help with (testing etc.). As it stands, the status is completely unclear apart from the statement _to be patient_ - without indicating what the actual point is where things are stuck. -- 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/1766137 Title: [regression] Password accepted but login fails (blank purple screen and mouse pointer only) Status in gdm: Fix Released Status in Release Notes for Ubuntu: Fix Released Status in gdm3 package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Invalid Status in gdm3 source package in Bionic: Fix Committed Status in gnome-shell source package in Bionic: Invalid Bug description: [ Description ] Due to a refcounting bug, a GDBusConnection was getting disposed when it was still required. The symptom of this was that you couldn't log in on the second attempt if you'd got your password wrong on the first attempt. All you'd see is a blank purple screen and mouse pointer only. [ Test case ] 1. Boot to GDM 2. Click your username 3. Type the wrong password a couple of times, pressing enter after each time 4. Type the right password If the bug is happening, after 4. the system hangs at a blank screen with the mouse cursor. If you then switch to a VT or otherwise connect to the machine, you can examine the journal and you'll see a G_IS_DBUS_CONNECTION failure. [ Fix ] Marco and I worked upstream on this fix. We found out that there was a problem like this- The GdmClient has a shared GDBusConnection for its operations. The first time someone calls for it, it is created and stored in the object's private structure. Subsequent calls return *a new reference* to this same object. It turned out that the asynchronous method to get the connection was accidentally unreferencing its object before giving it to the caller if it was returning an already-existing connection. For this to work properly, we need to nullify the pointer we stored when the connection goes away, so we know when to make a new one. There were some cases where we didn't add the weak references required to do that. Those are also fixed. [ Regression potential ] Now we share connections more than we did before. We also more carefully track when to clear our object. If we got this wrong, we might end up leaking the connection or dropping it in even more cases. [ Original report ] WORKAROUND: After typing an incorrect password, click Cancel, then click your name, then enter your password again. --- Trying to log into my session (Gnome, Xorg), if I enter the wrong password before entering it correctly, the session doesn't load and I get a purple screen, a mouse cursor, and an invisible but clickable menu in the top right. If I enter it correctly the first time, there is no problem. I've replicated this from a fresh boot, after logging out and after 'sudo service gdm restart' from the Ctrl-Alt-F4 console. This is a fresh install, and didn't occur when I was using a previous install of 18.04 (until Friday). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 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: ubuntu:GNOME Date: Sun Apr 22 20:31:13 2018 InstallationDate: Installed on 2018-04-22 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64
[Desktop-packages] [Bug 1776078] [NEW] Wrong display of calendar entries with different timezone for start and stop date
Public bug reported: Timezone of stop date is ignored for ics files and caldac calendars. The attached example has a during of 7 hours. It gets imported correctly with evolution. However, it looks like an event with a duration of one hour in the calendar. Thunderbird displays the event correctly (as my iPhone). Import creates error message if stop time in local timezone is 'before' start time in specified timezone (see second example). Event is not displayed in the regular calender view but can be seen in the list view. When I open the entry, I can only choose a timezone for the entire event, i.e., not for start and stop date separately. Expected behavior: - correct display of length of event in the calendar view - separate entry fields for timezones for start and stop date (cf. Thunderbird - Lightning) Example 1: BEGIN:VCALENDAR PRODID:-//Mozilla.org/NONSGML Mozilla Calendar V1.1//EN VERSION:2.0 BEGIN:VEVENT CREATED:20180610T131500Z LAST-MODIFIED:20180610T131418Z DTSTAMP:20180610T131418Z UID:20180610_JK_Test1 SUMMARY:New Test Appointment DTSTART;TZID=Europe/Berlin:20180610T13 DTEND;TZID=America/New_York:20180610T14 END:VEVENT END:VCALENDAR Example 2: BEGIN:VCALENDAR PRODID:-//Mozilla.org/NONSGML Mozilla Calendar V1.1//EN VERSION:2.0 BEGIN:VEVENT CREATED:20180610T131500Z LAST-MODIFIED:20180610T131418Z DTSTAMP:20180610T131418Z UID:20180610_JK_Test2 SUMMARY:Short Test Appointment DTSTART;TZID=Europe/Berlin:20180610T13 DTEND;TZID=America/New_York:20180610T11 END:VEVENT END:VCALENDAR ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: evolution 3.28.1-2 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jun 10 15:41:39 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2018-04-05 (65 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180403) SourcePackage: evolution UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: evolution (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "Test Appointment.ics" https://bugs.launchpad.net/bugs/1776078/+attachment/5150903/+files/Test%20Appointment.ics -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1776078 Title: Wrong display of calendar entries with different timezone for start and stop date Status in evolution package in Ubuntu: New Bug description: Timezone of stop date is ignored for ics files and caldac calendars. The attached example has a during of 7 hours. It gets imported correctly with evolution. However, it looks like an event with a duration of one hour in the calendar. Thunderbird displays the event correctly (as my iPhone). Import creates error message if stop time in local timezone is 'before' start time in specified timezone (see second example). Event is not displayed in the regular calender view but can be seen in the list view. When I open the entry, I can only choose a timezone for the entire event, i.e., not for start and stop date separately. Expected behavior: - correct display of length of event in the calendar view - separate entry fields for timezones for start and stop date (cf. Thunderbird - Lightning) Example 1: BEGIN:VCALENDAR PRODID:-//Mozilla.org/NONSGML Mozilla Calendar V1.1//EN VERSION:2.0 BEGIN:VEVENT CREATED:20180610T131500Z LAST-MODIFIED:20180610T131418Z DTSTAMP:20180610T131418Z UID:20180610_JK_Test1 SUMMARY:New Test Appointment DTSTART;TZID=Europe/Berlin:20180610T13 DTEND;TZID=America/New_York:20180610T14 END:VEVENT END:VCALENDAR Example 2: BEGIN:VCALENDAR PRODID:-//Mozilla.org/NONSGML Mozilla Calendar V1.1//EN VERSION:2.0 BEGIN:VEVENT CREATED:20180610T131500Z LAST-MODIFIED:20180610T131418Z DTSTAMP:20180610T131418Z UID:20180610_JK_Test2 SUMMARY:Short Test Appointment DTSTART;TZID=Europe/Berlin:20180610T13 DTEND;TZID=America/New_York:20180610T11 END:VEVENT END:VCALENDAR ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: evolution 3.28.1-2 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jun 10 15:41:39 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2018-04-05 (65 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180403) SourcePackage: evolution UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1776078/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 1776075] [NEW] Bluetooth Problem
Public bug reported: Ich kann Bluetooth nicht Aktivieren ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128 Uname: Linux 4.4.0-127-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sun Jun 10 14:59:59 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7400G] [1002:9994] (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd Trinity [Radeon HD 7400G] [144d:c660] InstallationDate: Installed on 2015-11-17 (935 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: SAMSUNG ELECTRONICS CO., LTD. 535U3C ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-127-generic.efi.signed root=UUID=5b7ab83e-d739-434f-afc7-78ed793a51a1 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/25/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P04RAS.W68.121025.LEO dmi.board.asset.tag: No Asset Tag dmi.board.name: NP535U3C-A03DE dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SEC_SW_REVISION_1234567890ABCD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP04RAS.W68.121025.LEO:bd10/25/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn535U3C:pvrP04RAS:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP535U3C-A03DE:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.name: 535U3C dmi.product.version: P04RAS dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sun Jun 10 14:07:04 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.7 xserver.video_driver: radeon ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- 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/1776075 Title: Bluetooth Problem Status in xorg package in Ubuntu: New Bug description: Ich kann Bluetooth nicht Aktivieren ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128 Uname: Linux 4.4.0-127-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sun Jun 10 14:59:59 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7400G] [1002:9994] (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd Trinity [Radeon HD 7400G] [144d:c660] InstallationDate: Installed on 2015-11-17 (935 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: SAMSUNG ELECTRONICS CO., LTD. 535U3C ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-127-generic.efi.signed root=UUID=5b7ab83e-d739-434f-afc7-78ed793a51a1 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/25/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P04RAS.W68.121025.LEO dmi.board.asset.tag: No Asset Tag dmi.board.name: NP535U3C-A03DE dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
[Desktop-packages] [Bug 1776069] [NEW] "Don't know how to handle 'file:///home//Downloads/.flatpakref'"
Public bug reported: After installing Flatpak and the plugin for GNOME Software, Flatpaks downloaded from the Flatpak website (flathub.org/apps) are not able to be opened in the GNOME Software Center, with the program giving me the following error: "Don't know how to handle 'file:///home//Downloads/.flatpakref'." ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-software 3.28.1-0ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jun 10 07:44:30 2018 InstallationDate: Installed on 2018-06-09 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InstalledPlugins: gnome-software-plugin-flatpak 3.28.1-0ubuntu4 gnome-software-plugin-limba N/A gnome-software-plugin-snap3.28.1-0ubuntu4 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) - >>> IDENTICAL BUG IN GNOME'S GITLAB: >>> https://gitlab.gnome.org/GNOME/gnome-software/issues/400/ <<< ** Affects: gnome-software Importance: Undecided Status: Confirmed ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug apps bionic ext extension flathub flatpak ** Changed in: gnome-software (Ubuntu) Status: New => Confirmed ** Summary changed: - "Don't know how to handle 'file:///home//Downloads/.flatpakref' + "Don't know how to handle 'file:///home//Downloads/.flatpakref'" ** Description changed: After installing Flatpak and the plugin for GNOME Software, Flatpaks downloaded from the Flatpak website (flathub.org/apps) are not able to be opened in the GNOME Software Center, with the program giving me the following error: - "Don't know how to handle 'file:///home//Downloads/.flatpakref' + "Don't know how to handle 'file:///home//Downloads/.flatpakref'." ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-software 3.28.1-0ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jun 10 07:44:30 2018 InstallationDate: Installed on 2018-06-09 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InstalledPlugins: - gnome-software-plugin-flatpak 3.28.1-0ubuntu4 - gnome-software-plugin-limba N/A - gnome-software-plugin-snap3.28.1-0ubuntu4 + gnome-software-plugin-flatpak 3.28.1-0ubuntu4 + gnome-software-plugin-limba N/A + gnome-software-plugin-snap3.28.1-0ubuntu4 ProcEnviron: - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: + IDENTICAL BUG IN GNOME'S GITLAB: https://gitlab.gnome.org/GNOME/gnome- + software/issues/400 + After installing Flatpak and the plugin for GNOME Software, Flatpaks downloaded from the Flatpak website (flathub.org/apps) are not able to be opened in the GNOME Software Center, with the program giving me the following error: "Don't know how to handle 'file:///home//Downloads/.flatpakref'." ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-software 3.28.1-0ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jun 10 07:44:30 2018 InstallationDate: Installed on 2018-06-09 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InstalledPlugins: gnome-software-plugin-flatpak 3.28.1-0ubuntu4 gnome-software-plugin-limba N/A gnome-software-plugin-snap3.28.1-0ubuntu4 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: - IDENTICAL BUG IN GNOME'S GITLAB: https://gitlab.gnome.org/GNOME/gnome- - software/issues/400 - After installing Flatpak and the plugin for GNOME Software, Flatpaks downloaded from the Flatpak website (flathub.org/apps) are not able to be opened in the GNOME Software Center, with the program giving me the following error: "Don't know how to handle 'file:///home//Downloads/.flatpakref'." ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-software 3.28.1-0ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64
[Desktop-packages] [Bug 1765261] Re: [regression] Ubuntu 18.04 login screen rejects a valid password on first attempt (if starting with Shift key). Usually works on the second attempt
I should have said that I am running Ubuntu 18.04 on a Dell XPS-13 9350, in case that is helpful. -- 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/1765261 Title: [regression] Ubuntu 18.04 login screen rejects a valid password on first attempt (if starting with Shift key). Usually works on the second attempt Status in gnome-shell package in Ubuntu: Triaged Status in gnome-shell source package in Bionic: Triaged Status in gnome-shell package in Fedora: Fix Released Bug description: Upstream: https://gitlab.gnome.org/GNOME/gnome-shell/issues/240 Workaround: Hit a lower-case key, then backspace, then enter your password. Original description: Ubuntu 18.04 login screen rejects a valid password on first attempt. Always works on the second attempt.. This seems to be a new problem, just started today. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 Date: Thu Apr 19 11:16:17 2018 InstallationDate: Installed on 2017-12-12 (127 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211) SourcePackage: gdm3 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/1765261/+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 1765261] Re: [regression] Ubuntu 18.04 login screen rejects a valid password on first attempt (if starting with Shift key). Usually works on the second attempt
I am experiencing the same issue as Vadim Peretokin above. I would agree that it appears to be a separate issue from the one discussed here -- it seems to have nothing to do with miscapitalization of the password (as revealed by "Show Text"). I have rarely experienced the issue at the first login screen but quite often at the lock screen. The only solution I have found is to reboot the machine (sometimes multiple times). I would prefer not to clutter up this discussion with an unrelated bug and can post a separate report but wanted see first if there was consensus that Vadim's and my issue sounds unrelated to the bug in this report. -- 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/1765261 Title: [regression] Ubuntu 18.04 login screen rejects a valid password on first attempt (if starting with Shift key). Usually works on the second attempt Status in gnome-shell package in Ubuntu: Triaged Status in gnome-shell source package in Bionic: Triaged Status in gnome-shell package in Fedora: Fix Released Bug description: Upstream: https://gitlab.gnome.org/GNOME/gnome-shell/issues/240 Workaround: Hit a lower-case key, then backspace, then enter your password. Original description: Ubuntu 18.04 login screen rejects a valid password on first attempt. Always works on the second attempt.. This seems to be a new problem, just started today. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 Date: Thu Apr 19 11:16:17 2018 InstallationDate: Installed on 2017-12-12 (127 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211) SourcePackage: gdm3 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/1765261/+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 1437502] Re: nautilus lacking 'new document' in context menu on GNOME
*** This bug is a duplicate of bug 1632027 *** https://bugs.launchpad.net/bugs/1632027 The workaround as suggested by Anders Hall is not very satisfactory because the first thing that you want to do after creating a new document is change the name. Previously, after creating the document you were immediately in a text field changing the name. Using the workaround, you have to select the document and select that you are changing the name before entering the name. It is pointless extra work. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1437502 Title: nautilus lacking 'new document' in context menu on GNOME Status in Ubuntu GNOME: Triaged Status in nautilus package in Ubuntu: Triaged Bug description: As the title mentions nautilus is provided in its default state and there is no 'New Document' in the context menu. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: nautilus 1:3.14.2-0ubuntu6 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 ApportVersion: 2.16.2-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Mar 27 17:49:01 2015 GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2015-03-27 (0 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Beta amd64 (20150326) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1437502/+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 1632027] Re: New Document feature missing from Nautilus 3.20+
The workaround as suggested by Steve G and others is not very satisfactory because the first thing that you want to do after creating a new document is change the name. Previously, after creating the document you were immediately in a text field so that you could change the name. Using the workaround, you have to select the document and select that you are changing the name before entering the name. It is pointless extra work. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1632027 Title: New Document feature missing from Nautilus 3.20+ Status in Nautilus: Invalid Status in nautilus package in Ubuntu: Confirmed Bug description: Ubuntu has a patch ( 16_unity_new_documents.patch ) to enable a 'New Document' function in the right-click context menu. This patch was not ported to Nautilus 3.20 so this Ubuntu-specific feature is missing in Ubuntu 16.10. https://bazaar.launchpad.net/~ubuntu- desktop/nautilus/ubuntu/view/head:/debian/patches/16_unity_new_documents.patch While this patch being disabled is noted in the debian/changelog, here's a formal bug to document the issue and maybe give it a bit more visibility so that it will be fixed. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: nautilus 1:3.20.3-1ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7 Uname: Linux 4.8.0-17-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Oct 10 12:54:50 2016 EcryptfsInUse: Yes GsettingsChanges: b'org.gnome.nautilus.preferences' b'open-folder-on-dnd-hover' b'false' b'org.gnome.nautilus.window-state' b'sidebar-width' b'171' b'org.gnome.nautilus.window-state' b'geometry' b"'1106x542+436+438'" b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'small'" InstallationDate: Installed on 2016-08-11 (59 days ago) InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Alpha amd64 (20160811) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1632027/+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 1776058] Re: gnome-shell crashed with signal 5
*** This bug is a duplicate of bug 1748450 *** https://bugs.launchpad.net/bugs/1748450 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1748450, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1776058/+attachment/5150810/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1776058/+attachment/5150812/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1776058/+attachment/5150816/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1776058/+attachment/5150817/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1776058/+attachment/5150818/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1776058/+attachment/5150819/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1776058/+attachment/5150820/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1748450 gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() from g_log() from ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1776058 Title: gnome-shell crashed with signal 5 Status in gnome-shell package in Ubuntu: New Bug description: I was informed by the relevant GNOME Shell extension that an update was available for Dash to Dock. I went to extensions.gnome.org to update it. The new version downloaded but my computer froze. I waited for GNOME Shell to recover which it did after a minute or so. The extension was switched off so I turned it on which prompted another download. The extension was then shown as having an error. I restarted GNOME Shell with "Alt+F2 >> r and enter" and shortly after received a prompt to report an issue which is what I am doing. Normal functionality with respect to turning the Dash to dock extension on and off has now resumed. ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.10-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Jun 10 10:03:51 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2017-11-07 (214 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash Signal: 5 SourcePackage: gnome-shell StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 g_settings_get_value () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 g_settings_get_boolean () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6 Title: gnome-shell crashed with signal 5 UpgradeStatus: Upgraded to cosmic on 2018-02-21 (108 days ago) UserGroups: adm cdrom dip kvm lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1776058/+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 1091663] Re: Support for Infineon modems
** Changed in: modemmanager Status: Confirmed => Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1091663 Title: Support for Infineon modems Status in ModemManager: Unknown Status in ubuntu-nexus7: Invalid Status in modemmanager package in Ubuntu: Triaged Bug description: Repeated attempts to get 3G connectivity on my Nexus 7 fail. The same SIM worked fine under Android. Very occasionally, a notification pops up saying that I have connected, but I am then immediately disconnected again. Most of the time, though, I get a 'disconnected' notification and nothing else. My provider is giffgaff (UK). The mobile broadband hardware is definitely detected by Ubuntu, given that it appears in the network menu. I can do further testing if asked. To manage notifications about this bug go to: https://bugs.launchpad.net/modemmanager/+bug/1091663/+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 1091663]
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mobile- broadband/ModemManager/issues/2. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1091663 Title: Support for Infineon modems Status in ModemManager: Unknown Status in ubuntu-nexus7: Invalid Status in modemmanager package in Ubuntu: Triaged Bug description: Repeated attempts to get 3G connectivity on my Nexus 7 fail. The same SIM worked fine under Android. Very occasionally, a notification pops up saying that I have connected, but I am then immediately disconnected again. Most of the time, though, I get a 'disconnected' notification and nothing else. My provider is giffgaff (UK). The mobile broadband hardware is definitely detected by Ubuntu, given that it appears in the network menu. I can do further testing if asked. To manage notifications about this bug go to: https://bugs.launchpad.net/modemmanager/+bug/1091663/+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 1771749] Re: Ethernet connection lost after few minutes since starting
What's kernel version do you use in Xenial LTS? -- 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/1771749 Title: Ethernet connection lost after few minutes since starting Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: This is the same bug I notified at Bug #1770848 but with a more precise selection of (what I think it is) the package affected and a better description. I made a few days ago a fresh install of the Kubuntu 18.04 LTS and it is most everything Ok, but -I think that- the network-manager has a problem. In the last LTS version, Kubuntu 16.04, nor in any Linux version if I remember well, I never lost connection through Ethernet (the only Internet connection with our desktop PC), but the Bionic Beaver loses the connection every now and then, perhaps within few minutes or hours, but several times per day. When the connection is lost, I note that it disappears any info even mention to any network into the network window and the network manager icon becomes red color. Not matter if I unplug and then plug the ethernet cable again, the ethernet connection is not longer detected and only restarting the PC makes the connection to work again. Incidentally, I also have noticed with this version of Kubuntu 18.04 that in my laptop there is also now a similar problem with the scanner: If I plug it in some USB port of the laptop once Kubuntu 18.04 is already running, it's not detected by Xsane. I have to plug it in before than pressing the power button or at the time of starting the OS, for the scanner to be detected by the scanning program (and then only works with Xsane, not if I use Simple Scan or Skanlite, even when it works under Xsane), as I said in the Bug #1771525 and, evenly, if I unplug the scanner cable from the USB port it is not detected anymore when plugging it again, and only restarting the laptop makes it to be detected. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: KDE Date: Thu May 17 08:24:23 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-05-11 (5 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IpRoute: default via 192.168.1.1 dev enp0s7 proto static metric 100 169.254.0.0/16 dev enp0s7 scope link metric 1000 192.168.1.0/24 dev enp0s7 proto kernel scope link src 192.168.1.3 metric 100 IwConfig: enp0s7no wireless extensions. lono wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true PciNetwork: RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE Conexión cableada 1 1cc37db8-0db8-3887-acf2-59fbbcd0cb1c ethernet 1526538083 jue 17 may 2018 08:21:23 CEST yes 4294967196 no/org/freedesktop/NetworkManager/Settings/1 yes enp0s7 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH enp0s7 ethernet connected /org/freedesktop/NetworkManager/Devices/2 Conexión cableada 1 1cc37db8-0db8-3887-acf2-59fbbcd0cb1c /org/freedesktop/NetworkManager/ActiveConnection/1 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nosotros 1116 F pulseaudio /dev/snd/controlC1: nosotros 1116 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=bb1531db-e7c0-48eb-a5b7-5afe3df47ba3 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet
[Desktop-packages] [Bug 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)
The conditions for the package to move to release are here: https://wiki.ubuntu.com/ProposedMigration#Migrating_packages_from_- proposed_to_release It's possible that the update breaks something in release, though I'm not sure what. It's also possible that we _just need to be more patient_, it's only been a few days since it was put in proposed. I don't see how spamming this bug is going to help the situation. -- 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/1766137 Title: [regression] Password accepted but login fails (blank purple screen and mouse pointer only) Status in gdm: Fix Released Status in Release Notes for Ubuntu: Fix Released Status in gdm3 package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Invalid Status in gdm3 source package in Bionic: Fix Committed Status in gnome-shell source package in Bionic: Invalid Bug description: [ Description ] Due to a refcounting bug, a GDBusConnection was getting disposed when it was still required. The symptom of this was that you couldn't log in on the second attempt if you'd got your password wrong on the first attempt. All you'd see is a blank purple screen and mouse pointer only. [ Test case ] 1. Boot to GDM 2. Click your username 3. Type the wrong password a couple of times, pressing enter after each time 4. Type the right password If the bug is happening, after 4. the system hangs at a blank screen with the mouse cursor. If you then switch to a VT or otherwise connect to the machine, you can examine the journal and you'll see a G_IS_DBUS_CONNECTION failure. [ Fix ] Marco and I worked upstream on this fix. We found out that there was a problem like this- The GdmClient has a shared GDBusConnection for its operations. The first time someone calls for it, it is created and stored in the object's private structure. Subsequent calls return *a new reference* to this same object. It turned out that the asynchronous method to get the connection was accidentally unreferencing its object before giving it to the caller if it was returning an already-existing connection. For this to work properly, we need to nullify the pointer we stored when the connection goes away, so we know when to make a new one. There were some cases where we didn't add the weak references required to do that. Those are also fixed. [ Regression potential ] Now we share connections more than we did before. We also more carefully track when to clear our object. If we got this wrong, we might end up leaking the connection or dropping it in even more cases. [ Original report ] WORKAROUND: After typing an incorrect password, click Cancel, then click your name, then enter your password again. --- Trying to log into my session (Gnome, Xorg), if I enter the wrong password before entering it correctly, the session doesn't load and I get a purple screen, a mouse cursor, and an invisible but clickable menu in the top right. If I enter it correctly the first time, there is no problem. I've replicated this from a fresh boot, after logging out and after 'sudo service gdm restart' from the Ctrl-Alt-F4 console. This is a fresh install, and didn't occur when I was using a previous install of 18.04 (until Friday). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 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: ubuntu:GNOME Date: Sun Apr 22 20:31:13 2018 InstallationDate: Installed on 2018-04-22 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180421.1) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1766137/+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 1767321] Re: Xorg freeze
Sebastien would https://wiki.ubuntu.com/DebuggingProgramCrash#The_Xorg_server catch this? This doesn't seem to be a 'crash'? So how should this be debugged? -- 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/1767321 Title: Xorg freeze Status in xorg package in Ubuntu: Incomplete Bug description: In Ubuntu 18.04, display freezes for ~1-5 seconds at seemingly random intervals. When it resumes, gnome shell's dock flickers as if the problem was caused by it. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17 Uname: Linux 4.15.0-20-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 27 20:02:51 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Skylake GT2 [HD Graphics 520] [103c:8079] Advanced Micro Devices, Inc. [AMD/ATI] Opal XT [Radeon R7 M265] [1002:6604] (rev 81) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Opal XT [Radeon R7 M265] [103c:814f] InstallationDate: Installed on 2018-04-03 (24 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180402) MachineType: HP HP EliteBook 850 G3 ProcKernelCmdLine: BOOT_IMAGE=/bionic/vmlinuz-4.15.0-20-lowlatency root=UUID=b6480aee-7c63-4ce4-9e8d-cdbef768b982 ro rootflags=subvol=@,relatime,autodefrag,space_cache quiet splash module.sig_enforce=1 intel_pstate=skylake_hwp radeon.si_support=0 radeon.cik_support=0 amdgpu.si_support=1 amdgpu.cik_support=1 vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/31/2016 dmi.bios.vendor: HP dmi.bios.version: N75 Ver. 01.10 dmi.board.name: 8079 dmi.board.vendor: HP dmi.board.version: KBC Version 85.6F dmi.chassis.asset.tag: 5CG6351LQL dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrN75Ver.01.10:bd07/31/2016:svnHP:pnHPEliteBook850G3:pvr:rvnHP:rn8079:rvrKBCVersion85.6F:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP EliteBook 850 G3 dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1767321/+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 405294] Re: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"]
Is it possible to backport fix which recently landed for bionic to xenial? -- 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/405294 Title: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"] Status in PulseAudio: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Bionic: Fix Released Bug description: SRU Request: [Impact] When the connection drops temporarily, using A2DP, a noticeable latency is introduced, and the audio goes out of sync. [Test Case] 1) Enable the -proposed repository, and install the new pulseaudio 2) Restart your computer, connect it to a bluetooth device (e.g. a headset or a speaker), play one or more videos either locally or online, and see if you can still reproduce the problem. [Regression Potential] Low, as the changes are upstream, and, if anything, it should also fix a memory leak. Furthermore, the changes only affect the bluez5-device module, in pulseaudio, and they make the buffer updating logic more conscious of how things can change when the connection drops. This is unlikely to affect anything else in pulseaudio. As I upgraded to the Karmic alpha, bluetooth audio (via a2dp) stopped working properly. It was working fine in Jaunty. My headphones are detected and configured by pulse, but the audio skips as if it's spending half of each second paused. Music is buffered so that after I click stop on rhythmbox (or whatever--it happens with whatever player I use) the audio continues until it's caught up. syslog is full of the following lines: Jul 27 08:55:45 carlin1 pulseaudio[3218]: alsa-source.c: Increasing minimal latency to 1.00 ms Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 15128 us (= 2668 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 36586 us (= 6452 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 35593 us (= 6276 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 36597 us (= 6452 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 32601 us (= 5748 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 32589 us (= 5748 bytes) in audio stream This is with bluez 4.45-0ubuntu4 pulseaudio1:0.9.15-4ubuntu2 0 pulseaudio version 1:0.9.16~test2-0ubuntu1~ppa3 from ubuntu-audio-dev didn't help. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/405294/+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
