[Desktop-packages] [Bug 1734541] Re: encrypted home-directory is not unmounted on logout
Ich bin ebenfalls davon betroffen. I confirm this issue is affecting me too. Das ist mein System: This are my system: Linux Mint 19 (Beta) 64Bit - based on Ubuntu 18.04 Cinnamon 3.8.4 Ecryptfs in use (Home - directory) kernel 4.15.0-22-generic x86_64 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1734541 Title: encrypted home-directory is not unmounted on logout Status in gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Bug description: Current Situation: If you log out from an user account with an encrypted home directory, it is not automatically unmounted and encrypted again. Expected behaviour: If I log out from an user account with an encrypted home directory, Id expect the homedir to be unmounted and encrypted again. Stepts to reproduce: log into an account with encrypted home directory. (lets call it: user) Log out again log into another account (which has sudo rights, lets call it: user2) and now enter the following into a terminal: user2@ubuntu: sudo su user2@ubuntu: ls -la /home/user you can see the files of the user Reasons: This is a security issue, because as a user you can reasonable expect your data to be safe, if you log out. if you would simply log in as another user but keep your data accessable you would simply switch user, instead of loggin out. Many users only suspend their laptop while carrying it with them. Logging out and suspending the user expects to have at least the home directory encrypted. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gdm3 3.26.1-3ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Nov 26 16:18:39 2017 EcryptfsInUse: Yes ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1734541/+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 1762509] Re: Sorry, Something went wrong
[Expired for gnome-software (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-software (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1762509 Title: Sorry, Something went wrong Status in gnome-software package in Ubuntu: Expired Bug description: Gnome software gives this message: Sorry, Something went wrong every time I launch it. Log: abr 09 15:42:58 JULIO dbus-daemon[1911]: Activating service name='org.gnome.Software' abr 09 15:42:58 JULIO dbus-daemon[1911]: Successfully activated service 'org.gnome.Software' abr 09 15:42:58 JULIO gnome-software[7870]: application has no ID set abr 09 15:42:59 JULIO gnome-software[7870]: plugin appstream took 0,9 seconds to do setup abr 09 15:42:59 JULIO gnome-software[7870]: enabled plugins: desktop-categories, systemd-updates, packagekit-local, fwupd, packagekit-offline, shell-extensions, ubuntuone, packagekit-upgrade, packagekit-refresh, packagekit-proxy, os-release, packagekit, appstream, hardcoded-popular, hardcoded-blacklist, flatpak, desktop-menu-path, hardcoded-featured, generic-updates, limba, packagekit-refine, steam, rewrite-resource, modalias, ubuntu-reviews, snap, packagekit-history, provenance, provenance-license, icons, key-colors, key-colors-metadata abr 09 15:42:59 JULIO gnome-software[7870]: disabled plugins: repos, dummy, dpkg, ostree, epiphany, odrs abr 09 15:42:59 JULIO gnome-software[7870]: running get-updates-historical with timeout=60 on plugin=packagekit-offline took 1ms abr 09 15:42:59 JULIO gnome-software[7870]: failed to set proxy: GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._pk_2dengine_2derror_2dquark.Code3: setting the proxy failed: failed to get the session abr 09 15:42:59 JULIO gnome-software[7870]: failed to set proxies: GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._pk_2dengine_2derror_2dquark.Code3: setting the proxy failed: failed to get the session abr 09 15:43:00 JULIO PackageKit[2381]: get-updates transaction /598_eacdcacc from uid 1000 finished with success after 612ms abr 09 15:43:00 JULIO dbus[890]: [system] Activating via systemd: service name='org.freedesktop.Limba' unit='limba.service' abr 09 15:43:00 JULIO systemd[1]: Starting Limba helper daemon... abr 09 15:43:00 JULIO limba-daemon[7884]: Acquired a message bus connection abr 09 15:43:00 JULIO dbus[890]: [system] Successfully activated service 'org.freedesktop.Limba' abr 09 15:43:00 JULIO systemd[1]: Started Limba helper daemon. abr 09 15:43:00 JULIO limba-daemon[7884]: Acquired the name org.freedesktop.Limba abr 09 15:43:00 JULIO gnome-software[7870]: running refresh with failure-flags=use-events with timeout=60 with cache age=any on plugin=steam took 820ms abr 09 15:43:00 JULIO gnome-software[7870]: failed to call gs_plugin_add_installed on shell-extensions: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface 'org.gnome.Shell.Extensions' on object at path /org/gnome/Shell abr 09 15:43:00 JULIO gnome-software[7870]: running get-distro-updates with refine-flags=require-version,require-setup-action,require-update-details,require-upgrade-removed,require-provenance,require-icon with failure-flags=use-events with timeout=60 on plugin=appstream took 1ms abr 09 15:43:00 JULIO gnome-software[7870]: running refine with refine-flags=require-version,require-update-details,require-provenance,require-icon with failure-flags=fatal-any with timeout=60 on apps */*/*/os-upgrade/ubuntu.www.Ubuntu-17.10/* took 6ms abr 09 15:43:00 JULIO gnome-software[7870]: running get-recent with refine-flags=require-rating,require-icon with failure-flags=use-events with timeout=60 with max-results=20 with cache age=5184000 on plugin=flatpak took 6ms abr 09 15:43:00 JULIO gnome-software[7870]: running get-category-apps with refine-flags=require-rating,require-icon with failure-flags=use-events with timeout=60 with max-results=20 with category=audio-video/featured on plugin=flatpak took 7ms abr 09 15:43:00 JULIO gnome-software[7870]: running get-category-apps with refine-flags=require-rating,require-icon with failure-flags=use-events with timeout=60 with max-results=20 with category=games/featured on plugin=flatpak took 7ms abr 09 15:43:00 JULIO gnome-software[7870]: g_hash_table_get_values: assertion 'hash_table != NULL' failed abr 09 15:43:00 JULIO gnome-software[7870]: running get-updates with refine-flags=require-version,require-update-details,require-provenance,require-icon with failure-flags=use-events with timeout=60 on plugin=limba took 40ms abr 09 15:43:00 JULIO gnome-software[7870]: Only 0 apps for recent list, hiding abr 09 15:43:00 JULIO gnome-software[7870]: hiding category audio-video featured applications: found only 0 to show, need at least 9 abr 09 15:43:00 JULIO
[Desktop-packages] [Bug 1776044] [NEW] nvidia-340 crashes display in 18.04 Bionic when no Nvidia GPU present
Public bug reported: Upgrading to 18.04 (Bionic) desktop on a machine running 17.10 (Artful) and originally installed with Xenial 16.04. Previous release (and other) upgrades had gone without issue. Run the installer, upgrades to 18.04, and reboots. Instead of returning to graphical Ubuntu login prompt, booting starts but gets stuck in a state where the screen is flashing every few seconds between light grey and black. After various experimentation, discovered that the graphical login prompt would return as wanted if I did: sudo apt-get remove nvidia-340 Note - the machine has Intel graphics, HD Graphics 630 (rev 04). Why was nvidia-340 ever installed? I believe I setup this machine by exporting a package list from another machine that DID have nvidia graphics and then importing it (via synaptics package manager) to the machine in question. I believe that nvidia drivers have been installed for all the earlier Ubuntu releases, but only in 18.04 did they cause an issue. I tested this theory on another machine with Intel graphics running 18.04, and sure enough installing nvidia-340 broke the graphical login prompt on reboot - and removing nvidia-340 fixed it again. ProblemType: Bug 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.2 Architecture: amd64 Date: Sat Jun 9 18:47:58 2018 InstallationDate: Installed on 2017-06-30 (345 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: nvidia-graphics-drivers-340 UpgradeStatus: Upgraded to bionic on 2018-05-31 (10 days ago) ** Affects: nvidia-graphics-drivers-340 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug 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/1776044 Title: nvidia-340 crashes display in 18.04 Bionic when no Nvidia GPU present Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: Upgrading to 18.04 (Bionic) desktop on a machine running 17.10 (Artful) and originally installed with Xenial 16.04. Previous release (and other) upgrades had gone without issue. Run the installer, upgrades to 18.04, and reboots. Instead of returning to graphical Ubuntu login prompt, booting starts but gets stuck in a state where the screen is flashing every few seconds between light grey and black. After various experimentation, discovered that the graphical login prompt would return as wanted if I did: sudo apt-get remove nvidia-340 Note - the machine has Intel graphics, HD Graphics 630 (rev 04). Why was nvidia-340 ever installed? I believe I setup this machine by exporting a package list from another machine that DID have nvidia graphics and then importing it (via synaptics package manager) to the machine in question. I believe that nvidia drivers have been installed for all the earlier Ubuntu releases, but only in 18.04 did they cause an issue. I tested this theory on another machine with Intel graphics running 18.04, and sure enough installing nvidia-340 broke the graphical login prompt on reboot - and removing nvidia-340 fixed it again. ProblemType: Bug 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.2 Architecture: amd64 Date: Sat Jun 9 18:47:58 2018 InstallationDate: Installed on 2017-06-30 (345 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: nvidia-graphics-drivers-340 UpgradeStatus: Upgraded to bionic on 2018-05-31 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1776044/+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 1776040] [NEW] bug report
Public bug reported: fingerprint gui not responding ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sat Jun 9 23:35:24 2018 DistUpgraded: 2018-04-30 10:23:22,098 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21fa] InstallationDate: Installed on 2017-12-07 (184 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: LENOVO 23252EG ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=1c2e9f65-bfb0-4a84-98a0-3affb346ef44 ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-04-30 (40 days ago) dmi.bios.date: 09/09/2016 dmi.bios.vendor: LENOVO dmi.bios.version: G2ETA7WW (2.67 ) dmi.board.asset.tag: Not Available dmi.board.name: 23252EG dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ETA7WW(2.67):bd09/09/2016:svnLENOVO:pn23252EG:pvrThinkPadX230:rvnLENOVO:rn23252EG:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X230 dmi.product.name: 23252EG dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 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 1:2.10.5-1ubuntu1 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 xserver.bootTime: Mon Apr 30 01:11:48 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2~16.04.1 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic 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/1776040 Title: bug report Status in xorg package in Ubuntu: New Bug description: fingerprint gui not responding ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sat Jun 9 23:35:24 2018 DistUpgraded: 2018-04-30 10:23:22,098 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21fa] InstallationDate: Installed on 2017-12-07 (184 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: LENOVO 23252EG ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=1c2e9f65-bfb0-4a84-98a0-3affb346ef44 ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-04-30 (40 days ago) dmi.bios.date: 09/09/2016 dmi.bios.vendor: LENOVO dmi.bios.version: G2ETA7WW (2.67 ) dmi.board.asset.tag: Not Available dmi.board.name: 23252EG dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ETA7WW(2.67):bd09/09/2016:svnLENOVO:pn23252EG:pvrThinkPadX230:rvnLENOVO:rn23252EG:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X230 dmi.product.name: 23252EG dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO version.compiz: compiz
[Desktop-packages] [Bug 1761554] Re: [bionic] Extended characters in GNOME screen keyboard don't get entered
On 2018-06-09 22:08, Nicolas Schmitt wrote: > I feel like the update im-config 0.34-1ubuntu1.1 bugged out ibus-mozc > on Wayland. > > I'm getting crashes in LibreOffice---and in some other applications > (Gnome shell search bar), Thanks for reporting this. I can confirm it with ibus-mozc and LibreOffice. Same problem with ibus-libpinyin. (I think I only tested with gedit, where it works, before making the change...) Even if Wayland is not default in Ubuntu 18.04, this regression is too serious to be acceptable. I'm going to reverse the change. Thanks again! ** Changed in: im-config (Ubuntu) Status: Fix Released => In Progress ** Changed in: im-config (Ubuntu Bionic) Status: Fix Released => In Progress ** Changed in: im-config (Ubuntu Bionic) Importance: Medium => High ** Tags added: regression-update -- 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: In Progress 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 1776030] [NEW] Backup fails with "an unknown error"
Public bug reported:
Trying to a backup to a network drive. Yesterday Backup decided to do
the preiodic full backup. But it fails, and I get the following error
information with the "unknown error" message:
Traceback (innermost last):
File "/usr/bin/duplicity", line 1555, in
with_tempdir(main)
File "/usr/bin/duplicity", line 1541, in with_tempdir
fn()
File "/usr/bin/duplicity", line 1393, in main
do_backup(action)
File "/usr/bin/duplicity", line 1522, in do_backup
check_last_manifest(col_stats) # not needed for full backup
File "/usr/bin/duplicity", line 1227, in check_last_manifest
last_backup_set.check_manifests()
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 201,
in check_manifests
remote_manifest = self.get_remote_manifest()
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 242,
in get_remote_manifest
return manifest.Manifest().from_string(manifest_buffer)
File "/usr/lib/python2.7/dist-packages/duplicity/manifest.py", line 188, in
from_string
vi = VolumeInfo().from_string(match.group(1))
File "/usr/lib/python2.7/dist-packages/duplicity/manifest.py", line 388, in
from_string
raise VolumeInfoError("Start or end index not set")
VolumeInfoError: Start or end index not set
lsb_release -rd >
Description:Ubuntu 18.04 LTS
Release:18.04
apt-cache policy deja-dup >
deja-dup:
Installed: 37.1-2fakesync1
Candidate: 37.1-2fakesync1
Version table:
*** 37.1-2fakesync1 500
500 http://la-mirrors.evowise.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: deja-dup 37.1-2fakesync1
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: Sat Jun 9 21:14:08 2018
InstallationDate: Installed on 2016-02-26 (834 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
SourcePackage: deja-dup
UpgradeStatus: Upgraded to bionic on 2018-05-03 (37 days ago)
** Affects: deja-dup (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug bionic
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to deja-dup in Ubuntu.
https://bugs.launchpad.net/bugs/1776030
Title:
Backup fails with "an unknown error"
Status in deja-dup package in Ubuntu:
New
Bug description:
Trying to a backup to a network drive. Yesterday Backup decided to do
the preiodic full backup. But it fails, and I get the following error
information with the "unknown error" message:
Traceback (innermost last):
File "/usr/bin/duplicity", line 1555, in
with_tempdir(main)
File "/usr/bin/duplicity", line 1541, in with_tempdir
fn()
File "/usr/bin/duplicity", line 1393, in main
do_backup(action)
File "/usr/bin/duplicity", line 1522, in do_backup
check_last_manifest(col_stats) # not needed for full backup
File "/usr/bin/duplicity", line 1227, in check_last_manifest
last_backup_set.check_manifests()
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 201,
in check_manifests
remote_manifest = self.get_remote_manifest()
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 242,
in get_remote_manifest
return manifest.Manifest().from_string(manifest_buffer)
File "/usr/lib/python2.7/dist-packages/duplicity/manifest.py", line 188, in
from_string
vi = VolumeInfo().from_string(match.group(1))
File "/usr/lib/python2.7/dist-packages/duplicity/manifest.py", line 388, in
from_string
raise VolumeInfoError("Start or end index not set")
VolumeInfoError: Start or end index not set
lsb_release -rd >
Description: Ubuntu 18.04 LTS
Release: 18.04
apt-cache policy deja-dup >
deja-dup:
Installed: 37.1-2fakesync1
Candidate: 37.1-2fakesync1
Version table:
*** 37.1-2fakesync1 500
500 http://la-mirrors.evowise.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: deja-dup 37.1-2fakesync1
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: Sat Jun 9 21:14:08 2018
InstallationDate: Installed on 2016-02-26 (834 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
SourcePackage: deja-dup
UpgradeStatus: Upgraded to bionic on 2018-05-03 (37 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1776030/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe :
[Desktop-packages] [Bug 1761554] Re: [bionic] Extended characters in GNOME screen keyboard don't get entered
I feel like the update im-config 0.34-1ubuntu1.1 bugged out ibus-mozc on Wayland. I'm getting crashes in LibreOffice---and in some other applications (Gnome shell search bar), the candidate window is not showing up. It was definitely working at some point before this update. Could be that I'm wrong about this update causing this, I'm not really sure ... Someone else experiencing similar issues? -- 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: Fix Released 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 1756901] Re: GNOME Calendar crashes when I try to add my Google Calendar account
Hi, I have gnome-calendar 3.26.3 and I still experience this bug. Also, whenever I try to open it again it crashes after few seconds. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1756901 Title: GNOME Calendar crashes when I try to add my Google Calendar account Status in gnome-calendar package in Ubuntu: Confirmed Bug description: I clicked the following: Manage your calendars -> Calendar settings, which led me to the Settings program, the Online Accounts section, selected "Google account", entered my data. My data was successfully taken. GNOME Calendar did not load my calendar and crashed. Upon restarting GNOME Calendar/restarting Ubuntu, it did not load my calendar either. Clicking "Synchronise" did not fix the situation either. Why do I think this is a security vulnerability? I am just a Computer Science student, but I imagine something might possibly come in the way so that personal data could be taken. It happens if I run the vanilla gnome-session as well. -Ubuntu Bionic Beaver (development branch), 18.04, on a fresh install. -GNOME Calendar version: 3.28.0-1 (Version table: 3.28.0-1 500) -What I expected to happen: load my Google Calendar data. -What happened instead: crashed, didn't load my Google Calendar data, even if my Google account data is loaded my GNOME. I hope Apport uploaded the debug information properly. If not, I can try to recreate the bug and upload the debug data, if necessary. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-calendar 3.28.0-1 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 19 16:40:14 2018 ExecutablePath: /usr/bin/gnome-calendar InstallationDate: Installed on 2018-03-19 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180319) ProcCmdline: /usr/bin/gnome-calendar --gapplication-service SegvAnalysis: Segfault happened at: 0x7f3513ec4d12 : mov(%rdi),%rbp PC (0x7f3513ec4d12) ok source "(%rdi)" (0x2c6e616d656c6f63) not located in a known VMA region (needed readable region)! destination "%rbp" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-calendar StacktraceTop: g_type_check_instance_cast () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-calendar crashed with SIGSEGV in g_type_check_instance_cast() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1756901/+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 1767122] Re: duplicity Errors 199 at end backup
Yes, read the man page and pay attention to the 'cleanup' and 'remove-*' commands. With $ duplicity cleanup --force " you can clean out any partial backups taking up room. With $ duplicity remove-all-but-n-full 2 you can remove all but the last two backup sets. You should be able to tailor this to your backup disk size and backup plan. ** Changed in: duplicity Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1767122 Title: duplicity Errors 199 at end backup Status in Déjà Dup: New Status in Duplicity: Invalid Status in Python: New Status in duplicity package in Ubuntu: New Bug description: Hello, I use duplicity to backup my file. However. I get always this message at end backup with Error 199 --[ Backup Statistics ]-- StartTime 1524741993.34 (Thu Apr 26 13:26:33 2018) EndTime 1524746175.96 (Thu Apr 26 14:36:15 2018) ElapsedTime 4182.62 (1 hour 9 minutes 42.62 seconds) SourceFiles 3821570 SourceFileSize 191576839080 (178 GB) NewFiles 2088902 NewFileSize 19156070 (178 GB) DeletedFiles 3 ChangedFiles 54 ChangedFileSize 1834439 (1.75 MB) ChangedDeltaSize 0 (0 bytes) DeltaEntries 2088959 RawDeltaSize 0 (0 bytes) TotalDestinationSizeChange 0 (0 bytes) Errors 199lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04 LTS Release: 18.04 Codename: bionic Step to reproduce : 1. Configure duplicity 2. Run a bakup. Result 3. At end backup, you should get Error 199 - uname -r 4.15.0-20-generic My configuration : lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04 LTS Release: 18.04 Codename: bionic apt-cache policy duplicity duplicity: Installed: 0.7.17-0ubuntu1 Candidate: 0.7.17-0ubuntu1 Version table: *** 0.7.17-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status apt-cache policy python python: Installed: 2.7.15~rc1-1 Candidate: 2.7.15~rc1-1 Version table: *** 2.7.15~rc1-1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status Could you help me please to fix this issues ? Thanks by advance for your support Best regards Battant ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: duplicity 0.7.17-0ubuntu1 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: ubuntu:GNOME Date: Thu Apr 26 15:58:41 2018 SourcePackage: duplicity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/1767122/+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 1756901] Re: GNOME Calendar crashes when I try to add my Google Calendar account
Sorry for the confusion, I was using the snap version. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1756901 Title: GNOME Calendar crashes when I try to add my Google Calendar account Status in gnome-calendar package in Ubuntu: Confirmed Bug description: I clicked the following: Manage your calendars -> Calendar settings, which led me to the Settings program, the Online Accounts section, selected "Google account", entered my data. My data was successfully taken. GNOME Calendar did not load my calendar and crashed. Upon restarting GNOME Calendar/restarting Ubuntu, it did not load my calendar either. Clicking "Synchronise" did not fix the situation either. Why do I think this is a security vulnerability? I am just a Computer Science student, but I imagine something might possibly come in the way so that personal data could be taken. It happens if I run the vanilla gnome-session as well. -Ubuntu Bionic Beaver (development branch), 18.04, on a fresh install. -GNOME Calendar version: 3.28.0-1 (Version table: 3.28.0-1 500) -What I expected to happen: load my Google Calendar data. -What happened instead: crashed, didn't load my Google Calendar data, even if my Google account data is loaded my GNOME. I hope Apport uploaded the debug information properly. If not, I can try to recreate the bug and upload the debug data, if necessary. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-calendar 3.28.0-1 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 19 16:40:14 2018 ExecutablePath: /usr/bin/gnome-calendar InstallationDate: Installed on 2018-03-19 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180319) ProcCmdline: /usr/bin/gnome-calendar --gapplication-service SegvAnalysis: Segfault happened at: 0x7f3513ec4d12 : mov(%rdi),%rbp PC (0x7f3513ec4d12) ok source "(%rdi)" (0x2c6e616d656c6f63) not located in a known VMA region (needed readable region)! destination "%rbp" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-calendar StacktraceTop: g_type_check_instance_cast () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-calendar crashed with SIGSEGV in g_type_check_instance_cast() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1756901/+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 1776002] Re: Bug when switching between users
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1776002 When reporting bugs please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Package changed: ubuntu => gdm3 (Ubuntu) ** Tags added: bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1776002 Title: Bug when switching between users Status in gdm3 package in Ubuntu: New Bug description: Hello, In Ubuntu 18.04 there is a serious bug that manifests itself when switching between users. This is not every time, but often. When I try to switch to another user, after entering the password, I get a clean screen, there are no calls to the hard drive. The computer is reset by the reset button. Thank you. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1776002/+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 1776002] [NEW] Bug when switching between users
You have been subscribed to a public bug: Hello, In Ubuntu 18.04 there is a serious bug that manifests itself when switching between users. This is not every time, but often. When I try to switch to another user, after entering the password, I get a clean screen, there are no calls to the hard drive. The computer is reset by the reset button. Thank you. ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Bug when switching between users https://bugs.launchpad.net/bugs/1776002 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1765053] Re: Errors were encountered while processing: /tmp/apt-dpkg-install-x8YVfC/03-libnvidia-compute-390_390.48-0ubuntu2_i386.deb
Hello, The GUI (graphicc user interface)!dose not start If i have no internet connection (offline ) An other personé (novice on ubuntu ) has upgrade Ubuntu 16.04 to Ubuntu 18.04 Have the same probkeme The internet must connect at start (Ethernet or WiFi) Same problem whith the live dvd ? Why this internet connection deprndence Why the GUI coud’nt Start ofline Could you confirme this and help me to fix this issue Thanks for your supporters Best regards Battant -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1765053 Title: Errors were encountered while processing: /tmp/apt-dpkg-install- x8YVfC/03-libnvidia-compute-390_390.48-0ubuntu2_i386.deb Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in ubuntu-drivers-common package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 source package in Bionic: Confirmed Status in ubuntu-drivers-common source package in Bionic: Confirmed Bug description: Using Ubuntu MATE 18.04 daily ubuntu-drivers fails to install the nvidia 390 drivers. Here is what I captured on stdout. $ sudo ubuntu-drivers autoinstall Reading package lists... Done Building dependency tree Reading state information... Done The following package was automatically installed and is no longer required: gnome-session-common Use 'sudo apt autoremove' to remove it. The following additional packages will be installed: libnvidia-cfg1-390 libnvidia-common-390 libnvidia-compute-390 libnvidia-compute-390:i386 libnvidia-decode-390 libnvidia-decode-390:i386 libnvidia-encode-390 libnvidia-encode-390:i386 libnvidia-fbc1-390 libnvidia-fbc1-390:i386 libnvidia-gl-390 libnvidia-gl-390:i386 libnvidia-ifr1-390 libnvidia-ifr1-390:i386 libwayland-client0:i386 libwayland-server0:i386 libxnvctrl0 nvidia-compute-390 nvidia-compute-no-dkms-390 nvidia-compute-utils-390 nvidia-dkms-390 nvidia-kernel-source-390 nvidia-settings nvidia-utils-390 screen-resolution-extra xserver-xorg-video-nvidia-390 The following NEW packages will be installed libnvidia-cfg1-390 libnvidia-common-390 libnvidia-compute-390 libnvidia-compute-390:i386 libnvidia-decode-390 libnvidia-decode-390:i386 libnvidia-encode-390 libnvidia-encode-390:i386 libnvidia-fbc1-390 libnvidia-fbc1-390:i386 libnvidia-gl-390 libnvidia-gl-390:i386 libnvidia-ifr1-390 libnvidia-ifr1-390:i386 libwayland-client0:i386 libwayland-server0:i386 libxnvctrl0 nvidia-compute-390 nvidia-compute-no-dkms-390 nvidia-compute-utils-390 nvidia-dkms-390 nvidia-driver-390 nvidia-kernel-source-390 nvidia-settings nvidia-utils-390 screen-resolution-extra xserver-xorg-video-nvidia-390 0 to upgrade, 27 to newly install, 0 to remove and 0 not to upgrade. Need to get 0 B/85.3 MB of archives. After this operation, 365 MB of additional disk space will be used. Selecting previously unselected package libnvidia-cfg1-390:amd64. (Reading database ... 258596 files and directories currently installed.) Preparing to unpack .../00-libnvidia-cfg1-390_390.48-0ubuntu2_amd64.deb ... Unpacking libnvidia-cfg1-390:amd64 (390.48-0ubuntu2) ... Selecting previously unselected package libnvidia-common-390. Preparing to unpack .../01-libnvidia-common-390_390.48-0ubuntu2_all.deb ... Unpacking libnvidia-common-390 (390.48-0ubuntu2) ... Selecting previously unselected package libnvidia-compute-390:amd64. Preparing to unpack .../02-libnvidia-compute-390_390.48-0ubuntu2_amd64.deb ... Unpacking libnvidia-compute-390:amd64 (390.48-0ubuntu2) ... Selecting previously unselected package libnvidia-compute-390:i386. Preparing to unpack .../03-libnvidia-compute-390_390.48-0ubuntu2_i386.deb ... Unpacking libnvidia-compute-390:i386 (390.48-0ubuntu2) ... dpkg: error processing archive /tmp/apt-dpkg-install-x8YVfC/03-libnvidia-compute-390_390.48-0ubuntu2_i386.deb (--unpack): trying to overwrite shared '/etc/OpenCL/vendors/nvidia.icd', which is different from other instances of package libnvidia-compute-390:i386 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Selecting previously unselected package libnvidia-decode-390:amd64. Preparing to unpack .../04-libnvidia-decode-390_390.48-0ubuntu2_amd64.deb ... Unpacking libnvidia-decode-390:amd64 (390.48-0ubuntu2) ... Selecting previously unselected package libnvidia-decode-390:i386. Preparing to unpack .../05-libnvidia-decode-390_390.48-0ubuntu2_i386.deb ... Unpacking libnvidia-decode-390:i386 (390.48-0ubuntu2) ... Selecting previously unselected package libnvidia-encode-390:i386. Preparing to unpack .../06-libnvidia-encode-390_390.48-0ubuntu2_i386.deb ... Unpacking libnvidia-encode-390:i386 (390.48-0ubuntu2) ... Selecting previously unselected package libnvidia-encode-390:amd64. Preparing to unpack .../07-libnvidia-encode-390_390.48-0ubuntu2_amd64.deb ... Unpacking
[Desktop-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display
Hello, The GUI (graphicc user interface)!dose not start If i have no internet connection (offline ) An other personé (novice on ubuntu ) has upgrade Ubuntu 16.04 to Ubuntu 18.04 Have the same probkeme The internet must connect at start (Ethernet or WiFi) Same problem whith the live dvd ? Why this internet connection deprndence Why the GUI coud’nt Start ofline Could you confirme this and help me to fix this issue Thanks for your supporters Best regards Battant -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1752053 Title: nvidia-390 fails to boot graphical display Status in mesa package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in xserver-xorg-video-nouveau package in Ubuntu: Invalid Bug description: I'm using Bionic with the new 4.15 kernel. I've been using the nvidia-384 driver with no problem for a while. Today I issued "sudo apt-get upgrade" and I was prompted to upgrade the nvidia driver to the nvidia-390. After installing the driver and rebooting, I was only able to boot in to the tty terminal. The graphical display failed to boot. I have had similar problems with nvidia driver version 390 with Arch Linux and with Open Suse Tumbleweed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+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 1642718] Re: At least 3-5 minute gap between removing power cable and system notifying of event
Launchpad has imported 3 comments from the remote bug at https://bugs.freedesktop.org/show_bug.cgi?id=98796. 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-11-20T13:58:53+00:00 Nikita Yerenkov-Scott wrote: I have noticed something very strange after upgrading to Ubuntu GNOME 16.10 with GNOME 3.22, and that is that if: - My laptop is fully charged and I remove the power cable: 1. The indicator in the top right hand side of the screen changes from the icon indicating that it is fully charged to the icon indicating that it is charging, but not fully charged. 2. In about 3-5 minutes (longer if I suspend my machine mid way during this time span) I will hear the noise which signifies that my machine has disconnected from the power cable and the icon will change to the normal one which indicates that the machine does not have a power cable attached to it (the time indicator will also show how long until the battery runs out instead of how long until it is fully charged). - My laptop is not fully charged and I remove the power cable: 1. The same happens as for the previous bullet point, however step 1 is skipped as it is not fully charged yet. - Either or the above bullet points, however I attach the power cable instead of removing it: 1. All of the expected (the noise and the icon change) happen immediately. I have described this with the Adwaita icon theme, however it is icon theme independent. If this is of any relevance, I have a Lenovo B590 laptop. I initially reported this issue here: https://bugs.launchpad.net/ubuntu- gnome/+bug/1642718 But thought I should also do so upstream. I first started off by reporting this issue to the upstream GNOME Shell project, however we established that the issue is in UPower rather than GNOME Shell: https://bugzilla.gnome.org/show_bug.cgi?id=774717#c7 Reply at: https://bugs.launchpad.net/ubuntu- gnome/+bug/1642718/comments/1 On 2016-11-20T13:59:41+00:00 Nikita Yerenkov-Scott wrote: I have UPower version 0.99.4-3 installed. Reply at: https://bugs.launchpad.net/ubuntu- gnome/+bug/1642718/comments/2 On 2018-06-04T13:24:12+00:00 Gitlab-migration wrote: -- 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/upower/upower/issues/31. Reply at: https://bugs.launchpad.net/ubuntu- gnome/+bug/1642718/comments/4 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1642718 Title: At least 3-5 minute gap between removing power cable and system notifying of event Status in Ubuntu GNOME: New Status in Upower: Unknown Status in upower package in Ubuntu: New Bug description: I have noticed something very strange after upgrading to Ubuntu GNOME 16.10 with GNOME 3.22, and that is that if: - My laptop is fully charged and I remove the power cable: 1. The indicator in the top right hand side of the screen changes from the icon indicating that it is fully charged to the icon indicating that it is charging, but not fully charged. 2. In about 3-5 minutes (longer if I suspend my machine mid way during this time span) I will hear the noise which signifies that my machine has disconnected from the power cable and the icon will change to the normal one which indicates that the machine does not have a power cable attached to it (the time indicator will also show how long until the battery runs out instead of how long until it is fully charged). - My laptop is not fully charged and I remove the power cable: 1. The same happens as for the previous bullet point, however step 1 is skipped as it is not fully charged yet. - Either or the above bullet points, however I attach the power cable instead of removing it: 1. All of the expected (the noise and the icon change) happen immediately. I have described this with the Adwaita icon theme, however it is icon theme independent. Related: Bug #1643190 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1642718/+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 1535030] Re: Can't recieve files from phone over Bluetooth
** Tags added: bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to obexd in Ubuntu. https://bugs.launchpad.net/bugs/1535030 Title: Can't recieve files from phone over Bluetooth Status in obexd package in Ubuntu: Confirmed Bug description: When I try to send files from my Android phone to my computer over Bluetooth, the phone connects successfully but then refuses to send the file with the error message "Transfer forbidden by target device". The following ends up in my /var/log/syslog: Jan 16 22:54:07 eristic obexd[2234]: CONNECT(0x0), (null)(0x) Jan 16 22:54:07 eristic obexd[2234]: CONNECT(0x0), (null)(0x0) Jan 16 22:54:07 eristic obexd[2234]: PUT(0x2), (null)(0x) Jan 16 22:54:07 eristic obexd[2234]: open(/home/sfreilich/Downloads/IMG_20160114 _121340.jpg): Operation not permitted (1) Jan 16 22:54:07 eristic obexd[2234]: PUT(0x2), FORBIDDEN(0x43) Jan 16 22:54:07 eristic gnome-session[1610]: ** (zeitgeist-datahub:2255): WARNIN G **: zeitgeist-datahub.vala:212: Error during inserting events: GDBus.Error:org .gnome.zeitgeist.EngineError.InvalidArgument: Incomplete event: interpretation, manifestation and actor are required Jan 16 22:54:07 eristic obexd[2234]: DISCONNECT(0x1), (null)(0x) Jan 16 22:54:07 eristic obexd[2234]: DISCONNECT(0x1), SUCCESS(0x20) Jan 16 22:54:07 eristic obexd[2234]: disconnected: Transport got disconnected Jan 16 22:54:07 eristic bluetoothd[664]: Unable to get io data for Object Push: getpeername: Transport endpoint is not connected (107) Strangely, the expected file is create in my Downloads folder, but the file is empty: $ ls -l ~/Downloads/ total 0 -rw--- 1 sfreilich sfreilich 0 Jan 16 22:54 IMG_20160114_121340.jpg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/obexd/+bug/1535030/+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 357007] Re: specify in the filename if the transfer is failed
fixed upstream about 5 years ago ** Changed in: gnome-user-share (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-user-share in Ubuntu. https://bugs.launchpad.net/bugs/357007 Title: specify in the filename if the transfer is failed Status in gnome-user-share: Fix Released Status in gnome-user-share package in Ubuntu: Fix Released Bug description: Binary package hint: gnome-user-share when receiving for instance a file named "test.txt", it is immediately called "test.txt". If the transfer fails, the user won't understand it. Maybe, as firefox does, the file should be named "test.txt.part", and them renamed to "test.txt" only when the transfer is finished To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-user-share/+bug/357007/+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 1776000] Re: gnome-control-center says "no bluetooth found" even though bluetooth is present and somewhat usable
** Description changed: I am running bionic and the gnome-control-center on the bluetooth tab tells me that "no bluetooth found" and that I should plug in a dongle to use bluetooth. My computer has built-in bluetooth. I believe I am seeing what's being discussed at http://gnome- apps.13852.n7.nabble.com/No-Bluetooth-Found-Plug-in-a-dongle-to-use- Bluetooth-td68467.html especially the message by Bjørn Forsman, dated Dec 31 2016. $ ll /dev/rfkill crw-rw-r--+ 1 root root 10, 62 Mai 29 17:19 /dev/rfkill $ bluetoothctl [NEW] Controller 3C:77:E6:EC:91:4E work [default] [NEW] Device 20:A9:0E:1B:1B:84 alcatel POP 4 Agent registered [bluetooth]# show Controller 3C:77:E6:EC:91:4E (public) - Name: work - Alias: work - Class: 0x0010010c - Powered: yes - Discoverable: yes - Pairable: yes - UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb) - UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) - UUID: OBEX File Transfer(1106--1000-8000-00805f9b34fb) - UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb) - UUID: OBEX Object Push (1105--1000-8000-00805f9b34fb) - UUID: PnP Information (1200--1000-8000-00805f9b34fb) - UUID: IrMC Sync (1104--1000-8000-00805f9b34fb) - UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) - UUID: Vendor specific (5005--1000-8000-0002ee01) - UUID: Message Notification Se.. (1133--1000-8000-00805f9b34fb) - UUID: Phonebook Access Server (112f--1000-8000-00805f9b34fb) - UUID: Message Access Server (1132--1000-8000-00805f9b34fb) - Modalias: usb:v1D6Bp0246d0530 - Discovering: yes + Name: work + Alias: work + Class: 0x0010010c + Powered: yes + Discoverable: yes + Pairable: yes + UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb) + UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) + UUID: OBEX File Transfer(1106--1000-8000-00805f9b34fb) + UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb) + UUID: OBEX Object Push (1105--1000-8000-00805f9b34fb) + UUID: PnP Information (1200--1000-8000-00805f9b34fb) + UUID: IrMC Sync (1104--1000-8000-00805f9b34fb) + UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) + UUID: Vendor specific (5005--1000-8000-0002ee01) + UUID: Message Notification Se.. (1133--1000-8000-00805f9b34fb) + UUID: Phonebook Access Server (112f--1000-8000-00805f9b34fb) + UUID: Message Access Server (1132--1000-8000-00805f9b34fb) + Modalias: usb:v1D6Bp0246d0530 + Discovering: yes $ rfkill list all 0: tpacpi_bluetooth_sw: Bluetooth - Soft blocked: no - Hard blocked: no + Soft blocked: no + Hard blocked: no 1: tpacpi_wwan_sw: Wireless WAN - Soft blocked: no - Hard blocked: no + Soft blocked: no + Hard blocked: no 2: phy0: Wireless LAN - Soft blocked: no - Hard blocked: no + Soft blocked: no + Hard blocked: no 30: hci0: Bluetooth - Soft blocked: no - Hard blocked: no + Soft blocked: no + Hard blocked: no + + This is what I see in /var/log/syslog when trying to send a file from a + paired phone. + + Jun 9 22:01:24 work obexd[18062]: CONNECT(0x0), (null)(0x) + Jun 9 22:01:24 work obexd[18062]: CONNECT(0x0), (null)(0x0) + Jun 9 22:01:24 work obexd[18062]: PUT(0x2), (null)(0x) + Jun 9 22:01:24 work obexd[18062]: PUT(0x2), FORBIDDEN(0x43) + Jun 9 22:01:24 work obexd[18062]: DISCONNECT(0x1), (null)(0x) + Jun 9 22:01:24 work obexd[18062]: DISCONNECT(0x1), SUCCESS(0x20) + Jun 9 22:01:24 work obexd[18062]: disconnected: Transport got disconnected + Jun 9 22:01:24 work bluetoothd[17556]: Unable to get io data for Object Push: getpeername: Transport endpoint is not connected (107) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1776000 Title: gnome-control-center says "no bluetooth found" even though bluetooth is present and somewhat usable Status in gnome-control-center package in Ubuntu: New Bug description: I am running bionic and the gnome-control-center on the bluetooth tab tells me that "no bluetooth found" and that I should plug in a dongle to use bluetooth. My computer has built-in bluetooth. I believe I am seeing what's being
[Desktop-packages] [Bug 1776000] [NEW] gnome-control-center says "no bluetooth found" even though bluetooth is present and somewhat usable
Public bug reported: I am running bionic and the gnome-control-center on the bluetooth tab tells me that "no bluetooth found" and that I should plug in a dongle to use bluetooth. My computer has built-in bluetooth. I believe I am seeing what's being discussed at http://gnome- apps.13852.n7.nabble.com/No-Bluetooth-Found-Plug-in-a-dongle-to-use- Bluetooth-td68467.html especially the message by Bjørn Forsman, dated Dec 31 2016. $ ll /dev/rfkill crw-rw-r--+ 1 root root 10, 62 Mai 29 17:19 /dev/rfkill $ bluetoothctl [NEW] Controller 3C:77:E6:EC:91:4E work [default] [NEW] Device 20:A9:0E:1B:1B:84 alcatel POP 4 Agent registered [bluetooth]# show Controller 3C:77:E6:EC:91:4E (public) Name: work Alias: work Class: 0x0010010c Powered: yes Discoverable: yes Pairable: yes UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb) UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) UUID: OBEX File Transfer(1106--1000-8000-00805f9b34fb) UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb) UUID: OBEX Object Push (1105--1000-8000-00805f9b34fb) UUID: PnP Information (1200--1000-8000-00805f9b34fb) UUID: IrMC Sync (1104--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: Vendor specific (5005--1000-8000-0002ee01) UUID: Message Notification Se.. (1133--1000-8000-00805f9b34fb) UUID: Phonebook Access Server (112f--1000-8000-00805f9b34fb) UUID: Message Access Server (1132--1000-8000-00805f9b34fb) Modalias: usb:v1D6Bp0246d0530 Discovering: yes $ rfkill list all 0: tpacpi_bluetooth_sw: Bluetooth Soft blocked: no Hard blocked: no 1: tpacpi_wwan_sw: Wireless WAN Soft blocked: no Hard blocked: no 2: phy0: Wireless LAN Soft blocked: no Hard blocked: no 30: hci0: Bluetooth Soft blocked: no Hard blocked: no ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1776000 Title: gnome-control-center says "no bluetooth found" even though bluetooth is present and somewhat usable Status in gnome-control-center package in Ubuntu: New Bug description: I am running bionic and the gnome-control-center on the bluetooth tab tells me that "no bluetooth found" and that I should plug in a dongle to use bluetooth. My computer has built-in bluetooth. I believe I am seeing what's being discussed at http://gnome- apps.13852.n7.nabble.com/No-Bluetooth-Found-Plug-in-a-dongle-to-use- Bluetooth-td68467.html especially the message by Bjørn Forsman, dated Dec 31 2016. $ ll /dev/rfkill crw-rw-r--+ 1 root root 10, 62 Mai 29 17:19 /dev/rfkill $ bluetoothctl [NEW] Controller 3C:77:E6:EC:91:4E work [default] [NEW] Device 20:A9:0E:1B:1B:84 alcatel POP 4 Agent registered [bluetooth]# show Controller 3C:77:E6:EC:91:4E (public) Name: work Alias: work Class: 0x0010010c Powered: yes Discoverable: yes Pairable: yes UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb) UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) UUID: OBEX File Transfer(1106--1000-8000-00805f9b34fb) UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb) UUID: OBEX Object Push (1105--1000-8000-00805f9b34fb) UUID: PnP Information (1200--1000-8000-00805f9b34fb) UUID: IrMC Sync (1104--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: Vendor specific (5005--1000-8000-0002ee01) UUID: Message Notification Se.. (1133--1000-8000-00805f9b34fb) UUID: Phonebook Access Server (112f--1000-8000-00805f9b34fb) UUID: Message Access Server (1132--1000-8000-00805f9b34fb) Modalias: usb:v1D6Bp0246d0530 Discovering: yes $ rfkill list all 0: tpacpi_bluetooth_sw: Bluetooth Soft blocked: no Hard blocked: no 1: tpacpi_wwan_sw: Wireless WAN Soft blocked: no Hard blocked: no 2: phy0: Wireless LAN Soft blocked: no Hard blocked: no 30: hci0: Bluetooth Soft blocked: no Hard blocked: no To manage notifications about this bug go to:
[Desktop-packages] [Bug 1775999] [NEW] Cannot set vino preferences in Lubuntu 18.04
Public bug reported: Apparently the functionality of vino-preferences was merged into gnome- control-center for 18.04. But since Lubuntu does not include gnome- control-center, there is no way to set up vino., ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: vino 3.22.0-3ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic i686 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: i386 CurrentDesktop: LXDE Date: Sat Jun 9 08:40:31 2018 InstallationDate: Installed on 2018-03-09 (91 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha i386 (20180306.1) SourcePackage: vino UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: vino (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug bionic i386 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vino in Ubuntu. https://bugs.launchpad.net/bugs/1775999 Title: Cannot set vino preferences in Lubuntu 18.04 Status in vino package in Ubuntu: New Bug description: Apparently the functionality of vino-preferences was merged into gnome-control-center for 18.04. But since Lubuntu does not include gnome-control-center, there is no way to set up vino., ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: vino 3.22.0-3ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic i686 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: i386 CurrentDesktop: LXDE Date: Sat Jun 9 08:40:31 2018 InstallationDate: Installed on 2018-03-09 (91 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha i386 (20180306.1) SourcePackage: vino UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vino/+bug/1775999/+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 947484] Re: gnome-control-center crashed with SIGSEGV in _gtk_widget_set_alloc_needed()
no longer but thanks ;) sob., 9 cze 2018, 15:19 użytkownik Rolf Leggewie <947...@bugs.launchpad.net> napisał: > still an issue in 2018? > > ** Changed in: gnome-control-center (Ubuntu) >Status: Confirmed => Incomplete > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (960645). > https://bugs.launchpad.net/bugs/947484 > > Title: > gnome-control-center crashed with SIGSEGV in > _gtk_widget_set_alloc_needed() > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/947484/+subscriptions > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/947484 Title: gnome-control-center crashed with SIGSEGV in _gtk_widget_set_alloc_needed() Status in gnome-control-center package in Ubuntu: Incomplete Bug description: during language setup - just after missing language packages has downloaded ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: gnome-control-center 1:3.3.90-0ubuntu4 ProcVersionSignature: Ubuntu 3.2.0-17.27-generic 3.2.6 Uname: Linux 3.2.0-17-generic i686 ApportVersion: 1.94-0ubuntu1 Architecture: i386 Date: Mon Mar 5 21:46:50 2012 ExecutablePath: /usr/bin/gnome-control-center InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) ProcCmdline: gnome-control-center --overview ProcEnviron: LANGUAGE=pl_PL:en PATH=(custom, no user) LANG=pl_PL.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x988c2a: mov%al,0x4(%edx) PC (0x00988c2a) ok source "%al" ok destination "0x4(%edx)" (0xaaae) in non-writable VMA region: 0xa981c000-0xad96f000 r--p /usr/share/icons/gnome/icon-theme.cache SegvReason: writing VMA /usr/share/icons/gnome/icon-theme.cache Signal: 11 SourcePackage: gnome-control-center StacktraceTop: ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0 gtk_widget_queue_resize () from /usr/lib/i386-linux-gnu/libgtk-3.so.0 Title: gnome-control-center crashed with SIGSEGV in gtk_widget_queue_resize() UpgradeStatus: Upgraded to precise on 2012-03-05 (0 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare usr_lib_gnome-control-center: activity-log-manager-control-center 0.9.2-0ubuntu3 deja-dup21.90-0ubuntu1 gnome-bluetooth 3.2.2-0ubuntu3 indicator-datetime 0.3.90-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/947484/+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 1177750] Re: gnome-control-center crash when click on network section
*** This bug is a duplicate of bug 951570 *** https://bugs.launchpad.net/bugs/951570 ** This bug has been marked a duplicate of bug 951570 [info]: gnome-control-center crashed with SIGSEGV in g_main_context_dispatch() -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1177750 Title: gnome-control-center crash when click on network section Status in gnome-control-center package in Ubuntu: Confirmed Bug description: gnome-control-center crash when click on network section need repeated trial (2-10 times) to reproduce the error. GDB Log: (gdb) attach ... ... (gdb) c Program received signal SIGSEGV, Segmentation fault. 0x7fe51f82f246 in nm_device_get_udi () from /usr/lib/libnm-glib.so.4 (gdb) bt #0 0x7fe51f82f246 in nm_device_get_udi () from /usr/lib/libnm-glib.so.4 #1 0x7fe51fee143a in ?? () from /usr/lib/control-center-1/panels/libnetwork.so #2 0x7fe5460a5ca2 in g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #3 0x7fe5460b6d71 in ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #4 0x7fe5460bf099 in g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #5 0x7fe5460bf242 in g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #6 0x7fe5460aa957 in ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #7 0x7fe5460ac233 in g_object_notify () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #8 0x7fe51f82808b in ?? () from /usr/lib/libnm-glib.so.4 #9 0x7fe545de8d53 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #10 0x7fe545de90a0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #11 0x7fe545de9164 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-control-center 1:3.4.2-0ubuntu0.11 ProcVersionSignature: Ubuntu 3.5.0-28.48~precise1-generic 3.5.7.9 Uname: Linux 3.5.0-28-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.2 Architecture: amd64 Date: Wed May 8 19:26:16 2013 InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130213) MarkForUpload: True ProcEnviron: LANGUAGE=en_HK:en TERM=xterm PATH=(custom, no user) LANG=en_HK.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: activity-log-manager-control-center 0.9.4-0ubuntu3.2 deja-dup22.0-0ubuntu4 gnome-bluetooth 3.2.2-0ubuntu5 indicator-datetime 0.3.94-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1177750/+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 985240] Re: [info]: gnome-control-center crashed with SIGSEGV in query_done()
*** This bug is a duplicate of bug 951570 *** https://bugs.launchpad.net/bugs/951570 ** This bug has been marked a duplicate of bug 951570 [info]: gnome-control-center crashed with SIGSEGV in query_done() -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/985240 Title: [info]: gnome-control-center crashed with SIGSEGV in query_done() Status in gnome-control-center package in Ubuntu: New Bug description: ATI ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: gnome-control-center 1:3.4.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic i686 NonfreeKernelModules: fglrx wl ApportVersion: 2.0.1-0ubuntu4 Architecture: i386 Date: Thu Apr 19 05:23:04 2012 ExecutablePath: /usr/bin/gnome-control-center InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012) ProcCmdline: gnome-control-center info SegvAnalysis: Segfault happened at: 0x11db6111:movl $0x0,0x24(%eax) PC (0x11db6111) ok source "$0x0" ok destination "0x24(%eax)" (0x3f24) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: ?? () from /usr/lib/control-center-1/panels/libinfo.so g_simple_async_result_complete () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0 Title: [info]: gnome-control-center crashed with SIGSEGV in g_simple_async_result_complete() UpgradeStatus: Upgraded to precise on 2012-04-18 (0 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare usr_lib_gnome-control-center: activity-log-manager-control-center 0.9.4-0ubuntu3 deja-dup22.0-0ubuntu2 gnome-bluetooth 3.2.2-0ubuntu5 indicator-datetime 0.3.94-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/985240/+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 948991] Re: [network]: gnome-control-center crashed with SIGSEGV in cc_shell_embed_widget_in_header()
*** This bug is a duplicate of bug 951570 *** https://bugs.launchpad.net/bugs/951570 still an issue in 2018? ** Changed in: gnome-control-center (Ubuntu) Status: Confirmed => Invalid ** Changed in: gnome-control-center (Ubuntu) Assignee: (unassigned) => Rolf Leggewie (r0lf) ** Changed in: gnome-control-center (Ubuntu) Status: Invalid => Incomplete ** This bug has been marked a duplicate of bug 951570 [info]: gnome-control-center crashed with SIGSEGV in query_done() -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/948991 Title: [network]: gnome-control-center crashed with SIGSEGV in cc_shell_embed_widget_in_header() Status in gnome-control-center package in Ubuntu: Incomplete Bug description: Description: Ubuntu precise (development branch) Release: 12.04 i'm not sure what caused crash, but it happend when i wanted to edit internet connection. when i press options on network manager it says "error initializing editor nm-settings-connection.c.839 - connection didn't have requested setting ppp". ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: gnome-control-center 1:3.3.91-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-18.28-generic 3.2.9 Uname: Linux 3.2.0-18-generic i686 ApportVersion: 1.94-0ubuntu2 Architecture: i386 Date: Wed Mar 7 15:07:27 2012 ExecutablePath: /usr/bin/gnome-control-center InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) ProcCmdline: gnome-control-center network ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0xe75ee7 : mov (%esi),%edi PC (0x00e75ee7) ok source "(%esi)" (0x7957ffa6) not located in a known VMA region (needed readable region)! destination "%edi" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: cc_shell_embed_widget_in_header () from /usr/lib/libgnome-control-center.so.1 ?? () from /usr/lib/control-center-1/panels/libnetwork.so ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 Title: [network]: gnome-control-center crashed with SIGSEGV in cc_shell_embed_widget_in_header() UpgradeStatus: Upgraded to precise on 2012-03-07 (0 days ago) UserGroups: adm debian-tor lpadmin sambashare sudo usr_lib_gnome-control-center: activity-log-manager-control-center 0.9.3-0ubuntu1 deja-dup21.90-0ubuntu1 gnome-bluetooth 3.2.2-0ubuntu3 indicator-datetime 0.3.90-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/948991/+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 876853] Re: gnome-control-center crashed with SIGSEGV in picture_scaled ()
** Changed in: gnome-control-center (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/876853 Title: gnome-control-center crashed with SIGSEGV in picture_scaled () Status in gnome-control-center: Fix Released Status in gnome-control-center package in Ubuntu: Fix Released Bug description: When clicking the Appearance option in the Gnome Control Centre, the application crashes with the stated error code. ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: gnome-control-center 1:3.2.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu3 Architecture: amd64 Date: Mon Oct 17 20:28:08 2011 ExecutablePath: /usr/bin/gnome-control-center ProcCmdline: gnome-control-center --overview ProcCwd: /home/scott ProcEnviron: PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fe06dbef1a0:mov0x8(%rax),%rcx PC (0x7fe06dbef1a0) ok source "0x8(%rax)" (0x0008) not located in a known VMA region (needed readable region)! destination "%rcx" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: ?? () from /usr/lib/control-center-1/panels/libbackground.so g_simple_async_result_complete () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-control-center crashed with SIGSEGV in g_simple_async_result_complete() UpgradeStatus: Upgraded to oneiric on 2011-10-15 (2 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare XsessionErrors: (nautilus:1831): Gtk-CRITICAL **: gtk_action_set_visible: assertion `GTK_IS_ACTION (action)' failed (nautilus:1831): Gtk-CRITICAL **: gtk_action_set_visible: assertion `GTK_IS_ACTION (action)' failed (gwibber-service:2203): libindicate-WARNING **: Menu being changed when the indicator is visible. Listeners will NOT be notified of this change. usr_lib_gnome-control-center: deja-dup 20.0-0ubuntu3 gnome-bluetooth3.2.0-0ubuntu1 indicator-datetime 0.3.0-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/876853/+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 964291] Re: [network]: gnome-control-center crashed with SIGSEGV in find_connection_for_device()
*** This bug is a duplicate of bug 951570 *** https://bugs.launchpad.net/bugs/951570 ** This bug has been marked a duplicate of bug 951570 [info]: gnome-control-center crashed with SIGSEGV in query_done() -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/964291 Title: [network]: gnome-control-center crashed with SIGSEGV in find_connection_for_device() Status in gnome-control-center package in Ubuntu: Confirmed Bug description: i dont know ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: gnome-control-center 1:3.3.92-0ubuntu4 ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.95-0ubuntu1 Architecture: amd64 Date: Sun Mar 25 07:40:32 2012 ExecutablePath: /usr/bin/gnome-control-center InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120318) ProcCmdline: gnome-control-center SegvReason: writing NULL VMA Signal: 11 SourcePackage: gnome-control-center Title: [network]: gnome-control-center crashed with SIGSEGV in g_main_context_dispatch() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/964291/+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 951570] Re: [info]: gnome-control-center crashed with SIGSEGV in query_done()
still an issue in 2018? ** Changed in: gnome-control-center (Ubuntu) Status: Confirmed => Incomplete ** Changed in: gnome-control-center (Ubuntu) Assignee: (unassigned) => Rolf Leggewie (r0lf) ** Summary changed: - [info]: gnome-control-center crashed with SIGSEGV in query_done() + [info]: gnome-control-center crashed with SIGSEGV in g_main_context_dispatch ** Summary changed: - [info]: gnome-control-center crashed with SIGSEGV in g_main_context_dispatch + [info]: gnome-control-center crashed with SIGSEGV in g_main_context_dispatch() -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/951570 Title: [info]: gnome-control-center crashed with SIGSEGV in g_main_context_dispatch() Status in gnome-control-center package in Ubuntu: Incomplete Bug description: I got this while trying to reproduce another bug. TO reproduce. Quickly open and close the icons in 'System Settings'. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: gnome-control-center 1:3.3.91-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9 Uname: Linux 3.2.0-18-generic x86_64 ApportVersion: 1.94.1-0ubuntu2 Architecture: amd64 CrashCounter: 1 Date: Sat Mar 10 16:01:52 2012 ExecutablePath: /usr/bin/gnome-control-center InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) ProcCmdline: gnome-control-center SegvAnalysis: Segfault happened at: 0x7f57af2d5470:movq $0x0,0x38(%rax) PC (0x7f57af2d5470) ok source "$0x0" ok destination "0x38(%rax)" (0xaae2) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: ?? () from /usr/lib/control-center-1/panels/libinfo.so g_simple_async_result_complete () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: [info]: gnome-control-center crashed with SIGSEGV in g_simple_async_result_complete() UpgradeStatus: Upgraded to precise on 2012-03-08 (2 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare usr_lib_gnome-control-center: activity-log-manager-control-center 0.9.3-0ubuntu1 deja-dup21.90-0ubuntu1 gnome-bluetooth 3.2.2-0ubuntu3 indicator-datetime 0.3.91-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/951570/+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 1259028] Re: [network]: gnome-control-center crashed with SIGSEGV in g_main_context_dispatch()
*** This bug is a duplicate of bug 951570 *** https://bugs.launchpad.net/bugs/951570 ** This bug is no longer a duplicate of bug 964291 [network]: gnome-control-center crashed with SIGSEGV in find_connection_for_device() ** This bug has been marked a duplicate of bug 951570 [info]: gnome-control-center crashed with SIGSEGV in query_done() -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1259028 Title: [network]: gnome-control-center crashed with SIGSEGV in g_main_context_dispatch() Status in gnome-control-center package in Ubuntu: New Bug description: I was just changing the proxy settings (it was launched through Chromium, the crash happened well after gnome-control-center started successfully and showed the GUI). The crash happened when I closed the program. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: gnome-control-center 1:3.4.2-0ubuntu0.13 ProcVersionSignature: Ubuntu 3.2.0-57.87-generic 3.2.52 Uname: Linux 3.2.0-57-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Sun Dec 8 19:36:15 2013 ExecutablePath: /usr/bin/gnome-control-center InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MarkForUpload: True ProcCmdline: gnome-control-center network SegvAnalysis: Segfault happened at: 0x7faee74cab00:cmp%r15,(%rax) PC (0x7faee74cab00) ok source "%r15" ok destination "(%rax)" (0x0001) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: ?? () from /usr/lib/control-center-1/panels/libnetwork.so ?? () from /usr/lib/control-center-1/panels/libnetwork.so ?? () from /usr/lib/control-center-1/panels/libnetwork.so g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: [network]: gnome-control-center crashed with SIGSEGV in g_main_context_dispatch() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo usr_lib_gnome-control-center: activity-log-manager-control-center 0.9.4-0ubuntu3.2 deja-dup22.0-0ubuntu4 gnome-bluetooth 3.2.2-0ubuntu5 indicator-datetime 0.3.94-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1259028/+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 1725414] Re: gnome-control-center crashed SIGSEGV in on_get_job_attributes_cb()
dupe of bug 951570? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1725414 Title: gnome-control-center crashed SIGSEGV in on_get_job_attributes_cb() Status in gnome-control-center package in Ubuntu: Confirmed Bug description: I started gtop and the system froze. Eventually I ended up in the login screen again. Problem is repeatable. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.26.1-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 20 13:14:52 2017 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2016-05-08 (530 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcCmdline: gnome-control-center printers ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 SegvAnalysis: Segfault happened at: 0x559ceda90e64:cmpq $0x0,0x8(%r12) PC (0x559ceda90e64) ok source "$0x0" ok destination "0x8(%r12)" (0x0008) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: ?? () ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-control-center crashed with SIGSEGV in g_main_context_dispatch() UpgradeStatus: Upgraded to artful on 2017-10-20 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1725414/+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 981426] Re: [network]: gnome-control-center crashed with SIGSEGV in nm_device_get_udi()
still an issue in 2018? ** Changed in: gnome-control-center (Ubuntu) Status: Confirmed => Incomplete ** Changed in: gnome-control-center (Ubuntu) Assignee: (unassigned) => Rolf Leggewie (r0lf) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/981426 Title: [network]: gnome-control-center crashed with SIGSEGV in nm_device_get_udi() Status in gnome-control-center package in Ubuntu: Incomplete Bug description: Opening the Appearance dialog ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: gnome-control-center 1:3.3.91-0ubuntu4 ProcVersionSignature: Ubuntu 3.2.0-19.30-generic-pae 3.2.11 Uname: Linux 3.2.0-19-generic-pae i686 NonfreeKernelModules: wl ApportVersion: 1.94.1-0ubuntu2 Architecture: i386 Date: Mon Mar 19 00:22:20 2012 ExecutablePath: /usr/bin/gnome-control-center InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta2 i386 (20120311) ProcCmdline: gnome-control-center --overv... ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: gnome-control-center 1:3.4.0-0ubuntu7 ProcVersionSignature: Ubuntu 3.2.0-20.33-generic-pae 3.2.12 Uname: Linux 3.2.0-20-generic-pae i686 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu2 Architecture: i386 Date: Sat Apr 14 16:00:21 2012 ExecutablePath: /usr/bin/gnome-control-center InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120328) ProcCmdline: gnome-control-center network ProcEnviron: LANGUAGE=zh_CN: PATH=(custom, no user) LANG=zh_CN.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0xb3170283 : cmp %eax,(%edx) PC (0xb3170283) ok source "%eax" ok destination "(%edx)" (0x0139) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: nm_device_get_udi () from /usr/lib/libnm-glib.so.4 ?? () from /usr/lib/control-center-1/panels/libnetwork.so g_cclosure_marshal_VOID__PARAM () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 g_closure_invoke () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 Title: [network]: gnome-control-center crashed with SIGSEGV in nm_device_get_udi() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo usr_lib_gnome-control-center: activity-log-manager-control-center 0.9.4-0ubuntu3 deja-dup22.0-0ubuntu2 gnome-bluetooth 3.2.2-0ubuntu5 indicator-datetime 0.3.94-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/981426/+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 948991] Re: [network]: gnome-control-center crashed with SIGSEGV in cc_shell_embed_widget_in_header()
*** This bug is a duplicate of bug 951570 *** https://bugs.launchpad.net/bugs/951570 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-control-center (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/948991 Title: [network]: gnome-control-center crashed with SIGSEGV in cc_shell_embed_widget_in_header() Status in gnome-control-center package in Ubuntu: Incomplete Bug description: Description: Ubuntu precise (development branch) Release: 12.04 i'm not sure what caused crash, but it happend when i wanted to edit internet connection. when i press options on network manager it says "error initializing editor nm-settings-connection.c.839 - connection didn't have requested setting ppp". ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: gnome-control-center 1:3.3.91-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-18.28-generic 3.2.9 Uname: Linux 3.2.0-18-generic i686 ApportVersion: 1.94-0ubuntu2 Architecture: i386 Date: Wed Mar 7 15:07:27 2012 ExecutablePath: /usr/bin/gnome-control-center InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) ProcCmdline: gnome-control-center network ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0xe75ee7 : mov (%esi),%edi PC (0x00e75ee7) ok source "(%esi)" (0x7957ffa6) not located in a known VMA region (needed readable region)! destination "%edi" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: cc_shell_embed_widget_in_header () from /usr/lib/libgnome-control-center.so.1 ?? () from /usr/lib/control-center-1/panels/libnetwork.so ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 Title: [network]: gnome-control-center crashed with SIGSEGV in cc_shell_embed_widget_in_header() UpgradeStatus: Upgraded to precise on 2012-03-07 (0 days ago) UserGroups: adm debian-tor lpadmin sambashare sudo usr_lib_gnome-control-center: activity-log-manager-control-center 0.9.3-0ubuntu1 deja-dup21.90-0ubuntu1 gnome-bluetooth 3.2.2-0ubuntu3 indicator-datetime 0.3.90-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/948991/+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 952399] Re: gnome-control-center crashed with SIGABRT in g_assertion_message()
*** This bug is a duplicate of bug 1765245 *** https://bugs.launchpad.net/bugs/1765245 ** This bug has been marked a duplicate of bug 1765245 gnome-control-center crashed with SIGABRT in g_assertion_message() (gvc_mixer_control_change_profile_on_selected_device) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/952399 Title: gnome-control-center crashed with SIGABRT in g_assertion_message() Status in gnome-control-center package in Ubuntu: New Bug description: Crash when open privacy and select all from drop down menu ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: gnome-control-center 1:3.3.91-0ubuntu3 ProcVersionSignature: Ubuntu 3.2.0-18.28-generic-pae 3.2.9 Uname: Linux 3.2.0-18-generic-pae i686 ApportVersion: 1.94.1-0ubuntu2 Architecture: i386 CrashCounter: 1 Date: Sun Mar 11 22:01:44 2012 ExecutablePath: /usr/bin/gnome-control-center InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120301) ProcCmdline: gnome-control-center activity-log-manager ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, user) LANG=en_IN SHELL=/bin/bash Signal: 6 SourcePackage: gnome-control-center StacktraceTop: raise () from /lib/i386-linux-gnu/libc.so.6 abort () from /lib/i386-linux-gnu/libc.so.6 g_assertion_message () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/i386-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0 Title: gnome-control-center crashed with SIGABRT in raise() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo usr_lib_gnome-control-center: activity-log-manager-control-center 0.9.3-0ubuntu1 deja-dup21.90-0ubuntu1 gnome-bluetooth 3.2.2-0ubuntu3 indicator-datetime 0.3.91-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/952399/+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 981426] Re: [network]: gnome-control-center crashed with SIGSEGV in nm_device_get_udi()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-control-center (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/981426 Title: [network]: gnome-control-center crashed with SIGSEGV in nm_device_get_udi() Status in gnome-control-center package in Ubuntu: Incomplete Bug description: Opening the Appearance dialog ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: gnome-control-center 1:3.3.91-0ubuntu4 ProcVersionSignature: Ubuntu 3.2.0-19.30-generic-pae 3.2.11 Uname: Linux 3.2.0-19-generic-pae i686 NonfreeKernelModules: wl ApportVersion: 1.94.1-0ubuntu2 Architecture: i386 Date: Mon Mar 19 00:22:20 2012 ExecutablePath: /usr/bin/gnome-control-center InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta2 i386 (20120311) ProcCmdline: gnome-control-center --overv... ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: gnome-control-center 1:3.4.0-0ubuntu7 ProcVersionSignature: Ubuntu 3.2.0-20.33-generic-pae 3.2.12 Uname: Linux 3.2.0-20-generic-pae i686 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu2 Architecture: i386 Date: Sat Apr 14 16:00:21 2012 ExecutablePath: /usr/bin/gnome-control-center InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120328) ProcCmdline: gnome-control-center network ProcEnviron: LANGUAGE=zh_CN: PATH=(custom, no user) LANG=zh_CN.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0xb3170283 : cmp %eax,(%edx) PC (0xb3170283) ok source "%eax" ok destination "(%edx)" (0x0139) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: nm_device_get_udi () from /usr/lib/libnm-glib.so.4 ?? () from /usr/lib/control-center-1/panels/libnetwork.so g_cclosure_marshal_VOID__PARAM () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 g_closure_invoke () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 Title: [network]: gnome-control-center crashed with SIGSEGV in nm_device_get_udi() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo usr_lib_gnome-control-center: activity-log-manager-control-center 0.9.4-0ubuntu3 deja-dup22.0-0ubuntu2 gnome-bluetooth 3.2.2-0ubuntu5 indicator-datetime 0.3.94-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/981426/+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 1348062] Re: bluetooth is disabled ( ralink 3290)
still an issue in bionic or later? ** Changed in: gnome-control-center (Ubuntu) Status: Confirmed => Incomplete ** Changed in: gnome-control-center (Ubuntu) Assignee: (unassigned) => Rolf Leggewie (r0lf) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1348062 Title: bluetooth is disabled ( ralink 3290) Status in gnome-control-center package in Ubuntu: Incomplete Bug description: OS: Ubutu 14.04 root@Viv-PC:/home/viv# apt-cache policy bluetooth bluetooth: Installed: (none) Candidate: 4.101-0ubuntu13 Version table: 4.101-0ubuntu13 0 500 http://archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages The combo button in HP laptop doesn't start blueooth (WiFI Works but not blinking) and there is no icon on the top right (control center) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1348062/+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 1057497] Re: [network]: gnome-control-center crashed with SIGSEGV in nm_device_get_udi()
*** This bug is a duplicate of bug 981426 *** https://bugs.launchpad.net/bugs/981426 ** This bug is no longer a duplicate of private bug 985191 ** This bug has been marked a duplicate of bug 981426 [network]: gnome-control-center crashed with SIGSEGV in nm_device_get_udi() -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1057497 Title: [network]: gnome-control-center crashed with SIGSEGV in nm_device_get_udi() Status in gnome-control-center package in Ubuntu: New Bug description: Here is what I did right before the crash: I opened the network settings, added an openvpn account, then connected to that account without first closing the network settings window. The network settings window then disappeared, but the connection was established successfully. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: gnome-control-center 1:3.4.2-0ubuntu0.5 Uname: Linux 3.5.4-zen+ x86_64 NonfreeKernelModules: apwr3_0 ApportVersion: 2.0.1-0ubuntu13 Architecture: amd64 Date: Thu Sep 27 14:29:06 2012 ExecutablePath: /usr/bin/gnome-control-center InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) ProcCmdline: gnome-control-center network ProcEnviron: PATH=(custom, user) LANG=de_DE.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7ffcf4577246 : cmp %rax,(%rdx) PC (0x7ffcf4577246) ok source "%rax" ok destination "(%rdx)" (0x05fb) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: nm_device_get_udi () from /usr/lib/libnm-glib.so.4 ?? () from /usr/lib/control-center-1/panels/libnetwork.so g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: [network]: gnome-control-center crashed with SIGSEGV in nm_device_get_udi() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip libvirtd lpadmin plugdev sambashare src sudo tracing vboxusers wireshark usr_lib_gnome-control-center: activity-log-manager-control-center 0.9.4-0ubuntu3 deja-dup22.0-0ubuntu2 gnome-bluetooth 3.2.2-0ubuntu5 indicator-datetime 0.3.94-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1057497/+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 1618751] Re: gnome-control-center crashed with SIGABRT in g_assertion_message()
*** This bug is a duplicate of bug 1765245 *** https://bugs.launchpad.net/bugs/1765245 ** This bug has been marked a duplicate of bug 1765245 gnome-control-center crashed with SIGABRT in g_assertion_message() (gvc_mixer_control_change_profile_on_selected_device) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1618751 Title: gnome-control-center crashed with SIGABRT in g_assertion_message() Status in gnome-control-center package in Ubuntu: Incomplete Bug description: Fter bluetooth manager crashed ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: gnome-control-center 1:3.20.1-2ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Aug 31 10:06:23 2016 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2016-08-29 (1 days ago) InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Alpha amd64 (20160823) ProcCmdline: gnome-control-center bluetooth ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=sl_SI.UTF-8 SHELL=/usr/bin/fish Signal: 6 SourcePackage: gnome-control-center StacktraceTop: g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgnome-bluetooth.so.13 ?? () from /usr/lib/x86_64-linux-gnu/libgnome-bluetooth.so.13 g_cclosure_marshal_VOID__OBJECTv () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-control-center crashed with SIGABRT in g_assertion_message() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1618751/+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 1765245] Re: gnome-control-center crashed with SIGABRT in g_assertion_message() (gvc_mixer_control_change_profile_on_selected_device)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-control-center (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1765245 Title: gnome-control-center crashed with SIGABRT in g_assertion_message() (gvc_mixer_control_change_profile_on_selected_device) Status in gnome-control-center package in Ubuntu: Confirmed Bug description: Crash occurred while JACK Audio was running and I was trying to switch output from Jack-sink to Bluetooth device. Description:Ubuntu Bionic Beaver (development branch) Release:18.04 4.15.0-17-generic #18-Ubuntu SMP Mon Apr 16 22:22:42 UTC 2018 gnome-control-center: Installed: 1:3.28.1-0ubuntu1 Candidate: 1:3.28.1-0ubuntu1 Version table: *** 1:3.28.1-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-17.18-generic 4.15.17 Uname: Linux 4.15.0-17-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 18 18:12:01 2018 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2018-03-03 (46 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180301) ProcCmdline: gnome-control-center --overview ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: gnome-control-center StacktraceTop: g_assertion_message () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 gvc_mixer_control_change_profile_on_selected_device () () () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-control-center crashed with SIGABRT in g_assertion_message() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1765245/+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 1036901] Re: gnome-control-center crashed with SIGSEGV in g_simple_async_result_complete()
still an issue in bionic or later? ** Changed in: gnome-control-center (Ubuntu) Status: Confirmed => Incomplete ** Changed in: gnome-control-center (Ubuntu) Assignee: (unassigned) => Rolf Leggewie (r0lf) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1036901 Title: gnome-control-center crashed with SIGSEGV in g_simple_async_result_complete() Status in gnome-control-center package in Ubuntu: Incomplete Bug description: On Quantal, this reliably crashes when I connect to a bluetooth speaker (Jambox) through bluetooth settings, then go to sound settings. ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: gnome-control-center 1:3.4.2-0ubuntu8 ProcVersionSignature: Ubuntu 3.5.0-6.6-generic 3.5.0 Uname: Linux 3.5.0-6-generic x86_64 ApportVersion: 2.4-0ubuntu6 Architecture: amd64 CrashCounter: 1 Date: Tue Aug 14 18:27:45 2012 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gnome-control-center InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120606.2) ProcCmdline: gnome-control-center bluetooth SegvAnalysis: Segfault happened at: 0x7f31620367a0:mov0x8(%rax),%rcx PC (0x7f31620367a0) ok source "0x8(%rax)" (0x0008) not located in a known VMA region (needed readable region)! destination "%rcx" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: ?? () from /usr/lib/libgnome-bluetooth.so.11 g_simple_async_result_complete () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 g_simple_async_result_complete () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: gnome-control-center crashed with SIGSEGV in g_simple_async_result_complete() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1036901/+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 960645] Re: gnome-control-center crashed with SIGSEGV in _gtk_widget_set_alloc_needed()
*** This bug is a duplicate of bug 947484 *** https://bugs.launchpad.net/bugs/947484 ** This bug has been marked a duplicate of bug 947484 gnome-control-center crashed with SIGSEGV in _gtk_widget_set_alloc_needed() -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/960645 Title: gnome-control-center crashed with SIGSEGV in _gtk_widget_set_alloc_needed() Status in gnome-control-center package in Ubuntu: New Bug description: gnome-control-center crashed with SIGSEGV in gtk_image_set_from_gicon() ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: gnome-control-center 1:3.3.92-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-19.30-generic 3.2.11 Uname: Linux 3.2.0-19-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.94.1-0ubuntu2 Architecture: amd64 Date: Tue Mar 20 22:37:51 2012 ExecutablePath: /usr/bin/gnome-control-center InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) ProcCmdline: gnome-control-center --overview SegvAnalysis: Segfault happened at: 0x7f1f7245b54a:movzbl 0x4(%rdx),%eax PC (0x7f1f7245b54a) ok source "0x4(%rdx)" (0xaaae) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 gtk_image_set_from_gicon () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: gnome-control-center crashed with SIGSEGV in gtk_image_set_from_gicon() UpgradeStatus: Upgraded to precise on 2012-03-20 (0 days ago) UserGroups: adm admin cdrom dialout lpadmin mythtv plugdev sambashare usr_lib_gnome-control-center: activity-log-manager-control-center 0.9.3-0ubuntu1 deja-dup21.90-0ubuntu1 gnome-bluetooth 3.2.2-0ubuntu3 indicator-datetime 0.3.91-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/960645/+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 947484] Re: gnome-control-center crashed with SIGSEGV in _gtk_widget_set_alloc_needed()
still an issue in 2018? ** Changed in: gnome-control-center (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/947484 Title: gnome-control-center crashed with SIGSEGV in _gtk_widget_set_alloc_needed() Status in gnome-control-center package in Ubuntu: Incomplete Bug description: during language setup - just after missing language packages has downloaded ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: gnome-control-center 1:3.3.90-0ubuntu4 ProcVersionSignature: Ubuntu 3.2.0-17.27-generic 3.2.6 Uname: Linux 3.2.0-17-generic i686 ApportVersion: 1.94-0ubuntu1 Architecture: i386 Date: Mon Mar 5 21:46:50 2012 ExecutablePath: /usr/bin/gnome-control-center InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) ProcCmdline: gnome-control-center --overview ProcEnviron: LANGUAGE=pl_PL:en PATH=(custom, no user) LANG=pl_PL.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x988c2a: mov%al,0x4(%edx) PC (0x00988c2a) ok source "%al" ok destination "0x4(%edx)" (0xaaae) in non-writable VMA region: 0xa981c000-0xad96f000 r--p /usr/share/icons/gnome/icon-theme.cache SegvReason: writing VMA /usr/share/icons/gnome/icon-theme.cache Signal: 11 SourcePackage: gnome-control-center StacktraceTop: ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0 gtk_widget_queue_resize () from /usr/lib/i386-linux-gnu/libgtk-3.so.0 Title: gnome-control-center crashed with SIGSEGV in gtk_widget_queue_resize() UpgradeStatus: Upgraded to precise on 2012-03-05 (0 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare usr_lib_gnome-control-center: activity-log-manager-control-center 0.9.2-0ubuntu3 deja-dup21.90-0ubuntu1 gnome-bluetooth 3.2.2-0ubuntu3 indicator-datetime 0.3.90-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/947484/+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 1036901] Re: gnome-control-center crashed with SIGSEGV in g_simple_async_result_complete()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-control-center (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1036901 Title: gnome-control-center crashed with SIGSEGV in g_simple_async_result_complete() Status in gnome-control-center package in Ubuntu: Incomplete Bug description: On Quantal, this reliably crashes when I connect to a bluetooth speaker (Jambox) through bluetooth settings, then go to sound settings. ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: gnome-control-center 1:3.4.2-0ubuntu8 ProcVersionSignature: Ubuntu 3.5.0-6.6-generic 3.5.0 Uname: Linux 3.5.0-6-generic x86_64 ApportVersion: 2.4-0ubuntu6 Architecture: amd64 CrashCounter: 1 Date: Tue Aug 14 18:27:45 2012 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gnome-control-center InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120606.2) ProcCmdline: gnome-control-center bluetooth SegvAnalysis: Segfault happened at: 0x7f31620367a0:mov0x8(%rax),%rcx PC (0x7f31620367a0) ok source "0x8(%rax)" (0x0008) not located in a known VMA region (needed readable region)! destination "%rcx" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: ?? () from /usr/lib/libgnome-bluetooth.so.11 g_simple_async_result_complete () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 g_simple_async_result_complete () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: gnome-control-center crashed with SIGSEGV in g_simple_async_result_complete() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1036901/+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 1681956] Re: gnome-user-share no longer provides gnome-user-share script
workaround from #4 does no longer seem to work in bionic. How can this be so screwed up in an LTS? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-user-share in Ubuntu. https://bugs.launchpad.net/bugs/1681956 Title: gnome-user-share no longer provides gnome-user-share script Status in gnome-user-share package in Ubuntu: Confirmed Bug description: Since users still have to get Bluetooth running manually following http://askubuntu.com/questions/131570/how-do-you-make-ubuntu-accept- files-sent-over-bluetooth because https://bugs.launchpad.net/ubuntu/+source/gnome-user- share/+bug/1406108 is still not fixed[1] there's need for the `gnome- user-share` script (usually `/usr/lib/gnome-user-share/gnome-user- share`). It's no longer provided by `gnome-user-share` and `apt-file find gnome-user-share` doesn't reveal any location where it could be now. As alternative, a thought-through intuitive bluetooth setup that not just somehow, but reliably works in all possible senses would be appreciated. --- [1] I Can't imagine anyone switching from the commercial OS who wouldn't go back the instant he_she started Ubuntu and was confronted with such an issue... ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gnome-user-share 3.14.2-2ubuntu5 ProcVersionSignature: Ubuntu 4.8.0-46.49-generic 4.8.17 Uname: Linux 4.8.0-46-generic x86_64 NonfreeKernelModules: zfs zunicode icp zcommon znvpair zavl ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Apr 11 23:55:27 2017 InstallationDate: Installed on 2015-12-12 (486 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gnome-user-share UpgradeStatus: Upgraded to yakkety on 2016-10-17 (176 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-user-share/+bug/1681956/+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 1278223] Re: Mouse Flickering after adding 3rd Monitor
Thanks Michael. Your solution works for me in combination with Workaround 1 of https://support.displaylink.com/knowledgebase/articles/1181623-displaylink-ubuntu-driver-after-recent-x-upgrades but with "PageFlip" line removed. -- 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/1278223 Title: Mouse Flickering after adding 3rd Monitor Status in xorg package in Ubuntu: Incomplete Bug description: *PLEASE READ FIRST BEFORE CONSIDERING MAKING A COMMENT* If you are having an issue and want it addressed, it is most helpful to file a new report. If you were led here by DisplayLink's website, you were led here in error as no useful debugging information has been provided by the original reporter, which is necessary to root cause, and solve the issue he reported. Posting comments about how you think you have the same problem isn't helpful here. My issues is, after adding a 3rd monitor to Ubuntu 14.04, the mouse flickers (or blinks) when the cursor is on monitors one or two, but not 3. Monitor 1: 1440 x 900 - Laptop's Native Monitor Monitor 2: 1920 x 1080 - Laptop's HDMI Port's External Monitor Monitor 3: 1024 x 768 - SIIG USB 2.0 to VGA Pro Monitor Here's the video card that feeds my laptop's native monitor, monitor 2 (hdmi). lspci | grep 'VGA\|Display' 00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07) 00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07) The 3rd Monitor is powered through a Display Link certified SIIG USB 2.0 to VGA Pro adapter (A2H1320X1374 - not sure what this number, but it is a sticker on back of the device): lsusb -tv /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 6: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M |__ Port 6: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M dmesg [1.688343] usb 2-1: New USB device found, idVendor=17e9, idProduct=02ee [1.688348] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [1.688351] usb 2-1: Product: VGA Display Adapter [1.688353] usb 2-1: Manufacturer: DisplayLink [1.688356] usb 2-1: SerialNumber: 119785 Additionally, unity-control-center crashes sometimes after I "Restore previous settings", after selecting a resolution too high. This freezed my laptop, requiring a hard reboot. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-control-center 14.04.1-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Feb 9 18:43:13 2014 InstallationDate: Installed on 2014-02-02 (7 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140202) SourcePackage: unity-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1278223/+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 1775989] Re: gnome-terminal-server crashed with SIGSEGV
*** This bug is a duplicate of bug 1664613 *** https://bugs.launchpad.net/bugs/1664613 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 #1664613, 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/1775989/+attachment/5150563/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1775989/+attachment/5150565/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1775989/+attachment/5150569/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1775989/+attachment/5150570/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1775989/+attachment/5150571/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1775989/+attachment/5150572/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1775989/+attachment/5150573/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1664613 ** 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-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1775989 Title: gnome-terminal-server crashed with SIGSEGV Status in gnome-terminal package in Ubuntu: New Bug description: Remmina was grabbing the XLock, I think. Then I started a gnome- terminal from the tty3 and I killed remmina from there. Then I think gnome-shell crashed and eventually gnome-terminal-server complained. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-terminal 3.24.2-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-44.49-generic 4.13.16 Uname: Linux 4.13.0-44-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jun 9 12:49:23 2018 ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server InstallationDate: Installed on 2017-10-13 (238 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171012) ProcCmdline: /usr/lib/gnome-terminal/gnome-terminal-server SegvAnalysis: Segfault happened at: 0x7fb1ac54f138:mov0x90(%r14),%rsi PC (0x7fb1ac54f138) ok source "0x90(%r14)" (0x0090) not located in a known VMA region (needed readable region)! destination "%rsi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-terminal StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 gdk_display_get_event () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: gnome-terminal-server crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1775989/+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 1767694] Re: Video streaming pauses frequently
same here, its not only on youtube, all streams that ive used so far present the same problem. Google Chrome. -- 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/1767694 Title: Video streaming pauses frequently Status in gnome-shell package in Ubuntu: Incomplete Bug description: When youtube is accessed, video often pauses while audio continues. This occurs every 10 or 20 seconds, and the video pauses between 3 and 7 seconds. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 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: ubuntu:GNOME Date: Sat Apr 28 14:50:47 2018 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2018-04-27 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1767694/+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 1775845] Re: gdm3 does not start on fresh 18.04 installation
** Package changed: gnome-shell (Ubuntu) => gdm3 (Ubuntu) ** Tags added: bionic -- 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/1775845 Title: gdm3 does not start on fresh 18.04 installation Status in gdm3 package in Ubuntu: New Bug description: I did a fresh 18.04 install on an fairly old HP USFF desktop with Intel Core2 Duo E7200, 4GB RAM DDR2 , but I could not boot, as the systems hangs right before the GDM start. The keyboard and mouse are not working as the "busy" hdd LED is running. After a couple of minutes like this, the system shuts itself down. I am writing this from a newly Debian 9.4 installation, as the 18.04 was not usable at all... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1775845/+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)
Hi, I'd like to test too - though being new here - can I (to avoid to switch to proposed repo) just download and install the AMD64 .deb files listed under proposed / 3.28.2-0ubuntu1.2 ? thanks, br, Koen -- 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 1775985] [NEW] No sound in bionic
Public bug reported: Dual-boot system Windows 10 / Ubuntu 18.04 LTS - Sound working in Windows but no sound card detected in Ubuntu. I've followed all troubleshooting steps on Ubuntu's alsa troubleshooting wiki. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Attachment added: "alsa-info-output.txt" https://bugs.launchpad.net/bugs/1775985/+attachment/5150555/+files/alsa-info-output.txt ** Description changed: Dual-boot system Windows 10 / Ubuntu 18.04 LTS - Sound working in Windows but no sound card detected in Ubuntu. I've followed all troubleshooting steps on Ubuntu's alsa troubleshooting wiki. - - $ bash alsa-info.sh --stdout - cat: /proc/asound/version: No such file or directory - grep: /proc/asound/cards: No such file or directory - cat: /proc/asound/cards: No such file or directory - lspci: Unable to load libkmod resources: error -12 - cat: /proc/asound/modules: No such file or directory - ls: cannot access '/dev/snd/*': No such file or directory - grep: /proc/asound/cards: No such file or directory - /usr/sbin/alsactl: save_state:1595: No soundcards found... - cat: /tmp/alsa-info.kAHvSVYxl9/alsactl.tmp: No such file or directory - upload=true=true= - !! - !!ALSA Information Script v 0.4.64 - !! - - !!Script ran on: Sat Jun 9 10:11:08 UTC 2018 - - - !!Linux Distribution - !!-- - - Ubuntu 18.04 LTS \n \l DISTRIB_ID=Ubuntu DISTRIB_DESCRIPTION="Ubuntu - 18.04 LTS" NAME="Ubuntu" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu - 18.04 LTS" HOME_URL="https://www.ubuntu.com/; - SUPPORT_URL="https://help.ubuntu.com/; - BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; - PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies - /privacy-policy" UBUNTU_CODENAME=bionic - - - !!DMI Information - !!--- - - Manufacturer: Gigabyte Technology Co., Ltd. - Product Name: GA-78LMT-USB3 - Product Version: - Firmware Version: FA - Board Vendor: Gigabyte Technology Co., Ltd. - Board Name:GA-78LMT-USB3 - - - !!ACPI Device Status Information - !!--- - - /sys/bus/acpi/devices/PNP0103:00/status15 - /sys/bus/acpi/devices/PNP0700:00/status15 - /sys/bus/acpi/devices/PNP0A03:00/status15 - /sys/bus/acpi/devices/PNP0C0C:00/status11 - /sys/bus/acpi/devices/PNP0C0F:00/status9 - /sys/bus/acpi/devices/PNP0C0F:01/status9 - /sys/bus/acpi/devices/PNP0C0F:02/status9 - /sys/bus/acpi/devices/PNP0C0F:03/status9 - /sys/bus/acpi/devices/PNP0C0F:04/status9 - /sys/bus/acpi/devices/PNP0C0F:05/status9 - /sys/bus/acpi/devices/PNP0C0F:06/status9 - /sys/bus/acpi/devices/PNP0C0F:07/status9 - /sys/bus/acpi/devices/device:0b/status 15 - /sys/bus/acpi/devices/device:0c/status 15 - /sys/bus/acpi/devices/device:0e/status 15 - /sys/bus/acpi/devices/device:0f/status 15 - - - !!Kernel Information - !!-- - - Kernel release:4.16.3+ - Operating System: GNU/Linux - Architecture: x86_64 - Processor: x86_64 - SMP Enabled: Yes - - - !!ALSA Version - !! - - Driver version: - Library version:1.1.3 - Utilities version: 1.1.3 - - - !!Loaded ALSA modules - !!--- - - - !!Sound Servers on this system - !! - - Pulseaudio: - Installed - Yes (/usr/bin/pulseaudio) - Running - Yes - - - !!Soundcards recognised by ALSA - !!- - - - !!PCI Soundcards installed in the system - !!-- - - 00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia (Intel HDA) - 01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Tahiti HDMI Audio [Radeon HD 7870 XT / 7950/7970] - - - !!Advanced information - PCI Vendor/Device/Subsystem ID's - !!--- - - 00:14.2 0403: 1002:4383 - Subsystem: 1458:a014 - -- - 01:00.1 0403: 1002:aaa0 - Subsystem: 1682:aaa0 - - - !!Modprobe options (Sound related) - !! - - snd_pcsp: index=-2 - snd_usb_audio: index=-2 - snd_atiixp_modem: index=-2 - snd_intel8x0m: index=-2 - snd_via82xx_modem: index=-2 - snd_atiixp_modem: index=-2 - snd_intel8x0m: index=-2 - snd_via82xx_modem: index=-2 - snd_usb_audio: index=-2 - snd_usb_caiaq: index=-2 - snd_usb_ua101: index=-2 - snd_usb_us122l: index=-2 - snd_usb_usx2y: index=-2 - snd_cmipci: mpu_port=0x330 fm_port=0x388 - snd_pcsp: index=-2 - snd_usb_audio: index=-2 - - - !!Loaded sound module options - !!--- - - - !!ALSA Device nodes - !!- - - - !!Aplay/Arecord output - !! - - APLAY - - aplay: device_list:270: no soundcards found... - - ARECORD - - arecord: device_list:270: no soundcards found... - - !!Amixer output -
[Desktop-packages] [Bug 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)
Hi, Tested the fix again - 3.28.2-0ubuntu1.2 on a fresh install of Ubuntu 18.04 LTS. I went through all scenarios: a) Login initially with incorrect password then correct password - Pass b) Login by entering incorrect password multiple times then correct password - Pass c) Created a second user (User B) then switched to that user entering correct password - Pass d) Switched back to User A entering correct password - Pass e) Switch between User A and B multiple times - Pass e) Switched to User B entering incorrect password first then correct password - Pass f) Switched to User A entering incorrect password first then correct password - Pass g) Performed logout of User A, then unlocked User B with correct password - Pass h) Performed logout of User B, then logged in to User A with correct password - Pass. Fix now works perfectly. All good. -- 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 1758652] Re: gsd-color[1116]: failed to set screen _ICC_PROFILE: Failed to open file “/home/oem/.local/share/icc/edid-***.icc”: Permission denied
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-settings-daemon (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1758652 Title: gsd-color[1116]: failed to set screen _ICC_PROFILE: Failed to open file “/home/oem/.local/share/icc/edid-***.icc”: Permission denied Status in gnome-settings-daemon package in Ubuntu: Confirmed Bug description: This is logged on that system using a /home partition: gsd-color[1116]: failed to set screen _ICC_PROFILE: Failed to open file “/home/oem/.local/share/icc/edid-.icc”: Permission denied oem@ubuntu:~$ ls -la /home/oem/.local/share/icc/ total 20 drwxrwxr-x 2 oem oem 4096 Feb 27 14:04 . drwxr-xr-x 32 oem oem 4096 Mar 25 10:43 .. -rw-rw-r-- 1 oem oem 1552 Feb 27 14:04 edid-***.icc ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-settings-daemon 3.28.0-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Mar 25 14:21:28 2018 EcryptfsInUse: Yes ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1758652/+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 1775978] [NEW] package texlive-latex-base (not installed) failed to install/upgrade: »/var/lib/tex-common/fmtutil-cnf/texlive/texlive-latex-base.cnf.dpkg-new« kann nicht geöffn
Public bug reported: error while installing texlive... ProblemType: Package DistroRelease: Ubuntu 18.04 Package: texlive-latex-base (not installed) 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 Date: Sat Jun 9 10:04:41 2018 ErrorMessage: »/var/lib/tex-common/fmtutil-cnf/texlive/texlive-latex-base.cnf.dpkg-new« kann nicht geöffnet werden: Vorgang nicht zulässig InstallationDate: Installed on 2018-06-08 (0 days ago) InstallationMedia: Xubuntu 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: texlive-base Title: package texlive-latex-base (not installed) failed to install/upgrade: »/var/lib/tex-common/fmtutil-cnf/texlive/texlive-latex-base.cnf.dpkg-new« kann nicht geöffnet werden: Vorgang nicht zulässig UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: texlive-base (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 texlive-base in Ubuntu. https://bugs.launchpad.net/bugs/1775978 Title: package texlive-latex-base (not installed) failed to install/upgrade: »/var/lib/tex-common/fmtutil-cnf/texlive/texlive-latex-base.cnf.dpkg- new« kann nicht geöffnet werden: Vorgang nicht zulässig Status in texlive-base package in Ubuntu: New Bug description: error while installing texlive... ProblemType: Package DistroRelease: Ubuntu 18.04 Package: texlive-latex-base (not installed) 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 Date: Sat Jun 9 10:04:41 2018 ErrorMessage: »/var/lib/tex-common/fmtutil-cnf/texlive/texlive-latex-base.cnf.dpkg-new« kann nicht geöffnet werden: Vorgang nicht zulässig InstallationDate: Installed on 2018-06-08 (0 days ago) InstallationMedia: Xubuntu 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: texlive-base Title: package texlive-latex-base (not installed) failed to install/upgrade: »/var/lib/tex-common/fmtutil-cnf/texlive/texlive-latex-base.cnf.dpkg-new« kann nicht geöffnet werden: Vorgang nicht zulässig UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texlive-base/+bug/1775978/+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 1775977] [NEW] Shotwell window disappears
Public bug reported: I was watching a photo. I press escape key and the shotwell window disappears (app still runing). Impossible to make the window visible again. After a moment, the app closes by itself ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: shotwell 0.28.2-0ubuntu1 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 CurrentDesktop: ubuntu:GNOME Date: Sat Jun 9 09:55:46 2018 InstallationDate: Installed on 2018-04-27 (42 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: shotwell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: shotwell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to shotwell in Ubuntu. https://bugs.launchpad.net/bugs/1775977 Title: Shotwell window disappears Status in shotwell package in Ubuntu: New Bug description: I was watching a photo. I press escape key and the shotwell window disappears (app still runing). Impossible to make the window visible again. After a moment, the app closes by itself ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: shotwell 0.28.2-0ubuntu1 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 CurrentDesktop: ubuntu:GNOME Date: Sat Jun 9 09:55:46 2018 InstallationDate: Installed on 2018-04-27 (42 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: shotwell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1775977/+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 1775957] Re: package tex-common 6.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
*** This bug is a duplicate of bug 1514474 *** https://bugs.launchpad.net/bugs/1514474 ** This bug has been marked a duplicate of bug 1514474 package tex-common 6.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tex-common in Ubuntu. https://bugs.launchpad.net/bugs/1775957 Title: package tex-common 6.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in tex-common package in Ubuntu: New Bug description: This happened in an automatic update ProblemType: Package DistroRelease: Ubuntu 16.04 Package: tex-common 6.04 ProcVersionSignature: Ubuntu 4.4.0-122.146-generic 4.4.117 Uname: Linux 4.4.0-122-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Fri Jun 8 19:13:09 2018 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20120703-2 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2013-11-06 (1675 days ago) InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20120703-15:08 PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: tex-common Title: package tex-common 6.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1775957/+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 1775974] [NEW] [Inspiron 530, Realtek ALC888, Black Line Out, Rear] Playback problem
Public bug reported: I have updated the software several times but the sound card is not seen on the settings. Seems a software bug? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: vincenzo 1138 F...m pulseaudio /dev/snd/controlC0: vincenzo 1138 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jun 9 08:12:53 2018 InstallationDate: Installed on 2018-05-02 (37 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful Symptom_Card: Built-in Audio - HDA Intel Symptom_Jack: Black Line Out, Rear Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [Inspiron 530, Realtek ALC888, Black Line Out, Rear] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/20/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.15 dmi.board.name: 0K216C dmi.board.vendor: Dell Inc. dmi.board.version: ��� dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: OEM dmi.modalias: dmi:bvnDellInc.:bvr1.0.15:bd06/20/2008:svnDellInc.:pnInspiron530:pvr:rvnDellInc.:rn0K216C:rvr:cvnDellInc.:ct3:cvrOEM: dmi.product.name: Inspiron 530 dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- 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/1775974 Title: [Inspiron 530, Realtek ALC888, Black Line Out, Rear] Playback problem Status in alsa-driver package in Ubuntu: New Bug description: I have updated the software several times but the sound card is not seen on the settings. Seems a software bug? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: vincenzo 1138 F...m pulseaudio /dev/snd/controlC0: vincenzo 1138 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jun 9 08:12:53 2018 InstallationDate: Installed on 2018-05-02 (37 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful Symptom_Card: Built-in Audio - HDA Intel Symptom_Jack: Black Line Out, Rear Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [Inspiron 530, Realtek ALC888, Black Line Out, Rear] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/20/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.15 dmi.board.name: 0K216C dmi.board.vendor: Dell Inc. dmi.board.version: ��� dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: OEM dmi.modalias: dmi:bvnDellInc.:bvr1.0.15:bd06/20/2008:svnDellInc.:pnInspiron530:pvr:rvnDellInc.:rn0K216C:rvr:cvnDellInc.:ct3:cvrOEM: dmi.product.name: Inspiron 530 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1775974/+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 1775972] [NEW] [System Product Name, Realtek ALC887-VD, Green Headphone Out, Front] No sound at all
Public bug reported: 1. lsb_release -rd Description:Ubuntu 18.04 LTS Release:18.04 2. alsa-utils: Installed: 1.1.3-1ubuntu1 Candidate: 1.1.3-1ubuntu1 Version table: *** 1.1.3-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status Installed: 1:11.1-1ubuntu7.1 Candidate: 1:11.1-1ubuntu7.1 Version table: *** 1:11.1-1ubuntu7.1 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:11.1-1ubuntu7 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.1 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.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: shooter2160 F pulseaudio /dev/snd/controlC0: shooter2160 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jun 9 12:24:21 2018 InstallationDate: Installed on 2018-05-29 (10 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm1627 F pulseaudio shooter2160 F pulseaudio /dev/snd/controlC0: gdm1627 F pulseaudio shooter2160 F pulseaudio Symptom_Jack: Green Headphone Out, Front Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [System Product Name, Realtek ALC887-VD, Green Headphone Out, Front] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/27/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3016 dmi.board.asset.tag: Default string dmi.board.name: H110M-CS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3016:bd12/27/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-CS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer modified.conffile..etc.pulse.daemon.conf: [modified] modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.daemon.conf: 2018-06-07T15:23:18.829781 mtime.conffile..etc.pulse.default.pa: 2018-06-07T15:56:30.613488 ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- 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/1775972 Title: [System Product Name, Realtek ALC887-VD, Green Headphone Out, Front] No sound at all Status in pulseaudio package in Ubuntu: New Bug description: 1. lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 2. alsa-utils: Installed: 1.1.3-1ubuntu1 Candidate: 1.1.3-1ubuntu1 Version table: *** 1.1.3-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status Installed: 1:11.1-1ubuntu7.1 Candidate: 1:11.1-1ubuntu7.1 Version table: *** 1:11.1-1ubuntu7.1 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:11.1-1ubuntu7 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.1 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.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: shooter2160 F pulseaudio /dev/snd/controlC0: shooter2160 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jun 9 12:24:21 2018 InstallationDate: Installed on 2018-05-29 (10 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA
