[Bug 1048121] Re: mythweb/php-mythtv incompatibility with PHP 5.4.x
The TL;DR for the below. To upgrade to the released 0.26 version for 12.10 mentioned in #9 you need to (note, this was done on a fairly recent clean install of 12.10 server amd64, although with a restored db backup from an old 0.25 install that had blown a disk, so the db was already populated): 1) Run: 'sudo add-apt-repository ppa:mythbuntu/0.26' 2) run 'sudo apt-get update; apt-get upgrade' 3) To fix the error in the update, edit the file at /var/lib/dpkg/info/mythtv-database.postinst, and around line 71 on, hardcode in your database name and mythtv username/password for the db (ref: http://www.mythtv.org/pipermail/mythtv-users/2012-October/340757.html) 4) Run: 'sudo dpkg --configure mythtv-database' and confirm the install finishes. 5) Finish updating any other components that didn't update above. 6) Edit /etc/mythtv/config.xml and ensure the settings match those in /etc/mythtv/mysql.txt. Myth no longer uses the mysql.txt file, but the updater doesn't seem to copy the settings over to the config.xml correctly. 7) Mythweb ends up broken and not loading. It got late by this point and I stopped trying to get it working. Option 2: 1) Go to: http://code.mythtv.org/trac/ticket/10504 and look at the patches there. 2) Manually apply the few lines of changes to your files. 3) Have working system. Ok, so I've attempted to update to 0.26 (I wasn't aware this is the currently supported version, I had assumed the latest version would come from the normal repos). After looking at the mythbuntu site in #9, the only install option that seemed obvious on that page was to install mythbuntu-control-centre and choose the version I wanted. When I looked at installing it, it wanted to pull in a bunch of X and python packages. Now I don't have a big concern about python, but pulling in a bunch of X seems silly on a headless server machine, just to select a repo. Looking around it was hard to be certain exactly which ppa I needed to enable, so I went with what is mentioned in #4 and managed to add what I think is the correct PPA. Now I seem to have hit the DB update issue mentioned in #5. To fix that I had to google to eventually find a thread from the mythtv-users mailing list that points out where the postinst script is for the mythtv-database package that breaks. For reference, page is at: http://www.mythtv.org/pipermail/mythtv-users/2012-October/340757.html Although I only had to change the database name, username and password, not all the values mentioned in that that. Then the mythtv-backend service wouldn't start up with an error about being unable to access the database. Luckly in my previous googling I noticed something about the mysql.txt file being deprecated in 0.26, and it instead reads the config from the config.xml file. So I checked /etc/mythtv/config.xml and /etc/mythtv/mysql.txt and found they had different settings. After copying over the correct password, and setting the host, db and user names, the backend will finally startup. However mythweb is still returning me errors and wont load. However, after also updating my frontend machine, I can at least record/watch shows and it's getting late, so I'm stopping here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1048121 Title: mythweb/php-mythtv incompatibility with PHP 5.4.x To manage notifications about this bug go to: https://bugs.launchpad.net/mythbuntu/+bug/1048121/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1048121] [NEW] mythweb/php-mythtv incompatibility with PHP 5.4.x
Public bug reported: After updating to the 12.10 development release, I can no longer use mythweb, any attempt to visit th emythweb page results in the following warning + error in my apache logs: [Sun Sep 09 15:03:04 2012] [error] [client x.x.x.x] PHP Warning: Unknown: function '0' not found or invalid function name in Unknown on line 0 [Sun Sep 09 15:03:04 2012] [error] [client x.x.x.x] PHP Fatal error: Call-time pass-by-reference has been removed in /usr/share/mythtv/bindings/php/MythBase.php on line 50 This appears to be a known issue upstream in MythTV ticket #10504 at: http://code.mythtv.org/trac/ticket/10504 My php version: ~# php --version PHP 5.4.6-1ubuntu1 (cli) (built: Aug 22 2012 21:13:52) Copyright (c) 1997-2012 The PHP Group Zend Engine v2.4.0, Copyright (c) 1998-2012 Zend Technologies The reported file from the apache error belongs to php-mythtv on Ubuntu: ~# dpkg-query -S /usr/share/mythtv/bindings/php/MythBase.php php-mythtv: /usr/share/mythtv/bindings/php/MythBase.php ** Affects: mythtv (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1048121 Title: mythweb/php-mythtv incompatibility with PHP 5.4.x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mythtv/+bug/1048121/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 794112] Re: Kerberos + LDAP + NFSv4 on Natty - Unable to recover unattended client
I installed the kernel build posted by Chris in #15, logged in as an LDAP user with KRB5 auth and a kerberised nfs4 home directory, then left the machine unattended for >24 hours. Under these conditions the X session would be locked up when I returned to the machine and the nfs mount inaccessable (if switching to a virtual console and logging in as a local user). This kernel seems to have mostly fixed things. This time I left the machine running with two terminals open, one showing the output of klist, so I could see when the ticket expired, the other running 'watch date'. I found the x session frozen a few seconds after the ticket expired. However, switching to a virtual console, I could log in as a local user and still access the nfs mount fine. There appeared to be now errors in the syslog (either now or around the time the ticket expired). Then still at the virtual console, I ssh'ed into this same box but as the ldap user, and logged in fine. When I then switched back to the X session it had unfrozen, although both terminal windows were gone and replaced with an error message telling me it had crashed. I'm not sure what caused the hung X session (or if it's still related to this bug), but the NFS mount seems to be handling ticket expiration better now. I should also mention that this machine does have machine credentials in Kerberos as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/794112 Title: Kerberos + LDAP + NFSv4 on Natty - Unable to recover unattended client To manage notifications about this bug go to: https://bugs.launchpad.net/kerberos/+bug/794112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 974664] Re: Kernel Oops - BUG: unable to handle kernel paging request at ffffffffffffffb8; RIP: 0010:[] [] nfs_have_delegation+0x9/0x40 [nfs]
I can confirm as well that using the kernel from #18 and performing the same steps as before fails to generate the bug and everything seems to work correctly. Thanks as well! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/974664 Title: Kernel Oops - BUG: unable to handle kernel paging request at ffb8; RIP: 0010:[] [] nfs_have_delegation+0x9/0x40 [nfs] To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/974664/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 981278] Re: Kernel Oops - BUG: unable to handle kernel paging request at ffffffffffffffb8; RIP: 0010:[] [] nfs_have_delegation+0x9/0x40 [nfs]
After a little bit of googling, it's possible this could be related to this thread: http://www.spinics.net/lists/linux-nfs/msg24949.html As soon as the process hangs and the log messages start I'm seeing a constant 5-9 mbit of network traffic in both directions between the client and server. Looking in the server logs however, I don't see anything interesting. It's possible this is related to the server-side kernel (which is running linux-image-3.2.0-23-generic as well). Unfortunately I can't take the server down right at the moment to test it with a newer kernel fixes it. I'll try to get around to it in a few days. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/981278 Title: Kernel Oops - BUG: unable to handle kernel paging request at ffb8; RIP: 0010:[] [] nfs_have_delegation+0x9/0x40 [nfs] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/981278/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 981278] Re: Kernel Oops - BUG: unable to handle kernel paging request at ffffffffffffffb8; RIP: 0010:[] [] nfs_have_delegation+0x9/0x40 [nfs]
That kernel has given some different behaviour. Now when open the file in lyx I get the following messages repeating over and over in the syslog: Apr 15 10:19:10 desktop kernel: [ 82.651314] NFS: nfs4_reclaim_open_state: Lock reclaim failed! Apr 15 10:19:10 desktop kernel: [ 82.652566] NFS: nfs4_reclaim_open_state: Lock reclaim failed! Apr 15 10:19:10 desktop kernel: [ 82.658018] NFS: nfs4_reclaim_open_state: Lock reclaim failed! Apr 15 10:19:10 desktop kernel: [ 82.659374] NFS: nfs4_reclaim_open_state: Lock reclaim failed! Apr 15 10:19:10 desktop kernel: [ 82.660565] NFS: nfs4_reclaim_open_state: Lock reclaim failed! Apr 15 10:19:10 desktop kernel: [ 82.661744] NFS: nfs4_reclaim_open_state: Lock reclaim failed! Apr 15 10:19:10 desktop kernel: [ 82.662970] NFS: nfs4_reclaim_open_state: Lock reclaim failed! Apr 15 10:19:10 desktop kernel: [ 82.664117] NFS: nfs4_reclaim_open_state: Lock reclaim failed! Apr 15 10:19:10 desktop kernel: [ 82.665189] NFS: nfs4_reclaim_open_state: Lock reclaim failed! Apr 15 10:19:10 desktop kernel: [ 82.666317] NFS: nfs4_reclaim_open_state: Lock reclaim failed! Apr 15 10:19:15 desktop kernel: [ 87.641236] nfs4_reclaim_open_state: 3923 callbacks suppressed No oops this time, but the lyx process is now hung. Ctrl-c at the terminal wouldn't kill it, but a kill -9 did. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/981278 Title: Kernel Oops - BUG: unable to handle kernel paging request at ffb8; RIP: 0010:[] [] nfs_have_delegation+0x9/0x40 [nfs] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/981278/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 981278] Re: Kernel Oops - BUG: unable to handle kernel paging request at ffffffffffffffb8; RIP: 0010:[] [] nfs_have_delegation+0x9/0x40 [nfs]
To add more information to this. If I start Lyx on its own (i.e. just 'lyx' at the command line, no file selected), then it starts fine. However if I then try to open a file I get the same behaviour as above. The above was triggered when doing 'lyx somefile.lyx' at the command line. This is probably not useful, but thought I would mention it. Next I installed linux- image-3.2.14-030214-generic_3.2.14-030214.201204021356_amd64.deb, rebooted into that kernel and got a similar error (see attached oops). I then install linux- image-3.2.15-030215-generic_3.2.15-030215.201204131303_amd64.deb and rebooted. This time the machine wouldn't come up. Choosing recovery mode in the Grub menu so I could see the kernel output, there were a couple of BUG/OOPS messages (the top scrolled of the screen so I couldn't see all of it). It appeared to be related to module loading/unloading. I was then left with some repeating udev messages about timeouts trying to do modprobes (I didn't write down the exact message). This seems unlrelated to this bug. As an interesting footnote, while I was editing the attached oops message in gedit, as I saved it into my homedir the same bug was triggered again, causing gedit to hang. Luckly it had actually written the file and I could access it fine. ** Attachment added: "3.2.14-generic.oops" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/981278/+attachment/3068423/+files/3.2.14-generic.oops ** Tags removed: needs-upstream-testing ** Tags added: kernel-bug-exists-upstream -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/981278 Title: Kernel Oops - BUG: unable to handle kernel paging request at ffb8; RIP: 0010:[] [] nfs_have_delegation+0x9/0x40 [nfs] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/981278/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 981278] Re: BUG: unable to handle kernel paging request at ffffffffffffffb8
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/981278 Title: BUG: unable to handle kernel paging request at ffb8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/981278/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 981278] [NEW] BUG: unable to handle kernel paging request at ffffffffffffffb8
Public bug reported: This was triggered by starting lyx, killing and trying again seemed to reproduce the error. Lyx would partially start, then hang. This was done as an LDAP/Kerberos user on a machine with an Kerberised NFS4 mounted home directory. ProblemType: KernelOops DistroRelease: Ubuntu 12.04 Package: linux-image-3.2.0-23-generic 3.2.0-23.36 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.0.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC3', '/dev/snd/hwC3D0', '/dev/snd/hwC3D1', '/dev/snd/hwC3D2', '/dev/snd/hwC3D3', '/dev/snd/pcmC3D3p', '/dev/snd/pcmC3D7p', '/dev/snd/pcmC3D8p', '/dev/snd/pcmC3D9p', '/dev/snd/controlC2', '/dev/snd/hwC2D0', '/dev/snd/hwC2D1', '/dev/snd/hwC2D2', '/dev/snd/hwC2D3', '/dev/snd/pcmC2D3p', '/dev/snd/pcmC2D7p', '/dev/snd/pcmC2D8p', '/dev/snd/pcmC2D9p', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D2p', '/dev/snd/by-path', '/dev/snd/by-id', '/dev/snd/controlC1', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xf3dd8000 irq 79' Mixer name : 'VIA VT2020' Components : 'HDA:11060441,1043846a,00100100' Controls : 47 Simple ctrls : 23 Card1.Amixer.info: Card hw:1 'LX3000'/'Microsoft LifeChat LX-3000 at usb-:00:1d.1-2, full speed' Mixer name : 'USB Mixer' Components : 'USB045e:070f' Controls : 7 Simple ctrls : 3 Card2.Amixer.info: Card hw:2 'NVidia'/'HDA NVidia at 0xf7ffc000 irq 34' Mixer name : 'Nvidia GPU 16 HDMI/DP' Components : 'HDA:10de0016,10de0101,00100100' Controls : 24 Simple ctrls : 4 Card3.Amixer.info: Card hw:3 'NVidia_1'/'HDA NVidia at 0xfbdfc000 irq 37' Mixer name : 'Nvidia GPU 16 HDMI/DP' Components : 'HDA:10de0016,10de0101,00100100' Controls : 24 Simple ctrls : 4 Date: Sat Apr 14 10:05:10 2012 Failure: oops InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-23-generic root=UUID=8abae32f-b353-49f7-b9d9-c747343e0b53 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon 0.12+git20090217-1ubuntu18 RfKill: SourcePackage: linux Title: BUG: unable to handle kernel paging request at ffb8 UpgradeStatus: Upgraded to precise on 2012-04-13 (0 days ago) dmi.bios.date: 05/11/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0901 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: Rampage III GENE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0901:bd05/11/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnRampageIIIGENE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-kerneloops kernel-driver-nfs kernel-oops precise -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/981278 Title: BUG: unable to handle kernel paging request at ffb8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/981278/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 870874] Re: LDAP user with automounted nfs homedir cannot login
I'm guessing the change linked to in #33 that fixes this is: * Remove 90qt-a11y: Qt accessibility is not stable enough in Oneiric to be enabled by default for all applications. A patch for unity-2d specifically enables accessibility for it so that the desktop remains accessible. (LP: #877358) And the next change: * Actually remove 90qt-a11y if it is already installed. I just upgraded to 12.04 and at-spi2-core version 2.4.0-1 and the 90qt- a11y file is back and exhibiting the same symptoms. So far I have found (always using an LDAP/Kerberos user with a Kerberised NFS4 home directory): Logging into the virtual console, and running the gsettings command from #3 and it prints "false" and hangs. Running gsettings under strace on the virtual console, it exits fine. Running gsettings from a terminal in X, it exits fine. Next I ran an instance at the virtual console and left it hung, then (after fetching the debug symbols) attached to the hung process with gdb. I find there's two threads: (gdb) thread find .* Thread 2 has target name 'dconf worker' Thread 2 has target id 'Thread 0x7f51717b5700 (LWP 22479)' Thread 1 has target name 'gsettings' Thread 1 has target id 'Thread 0x7f51779fc7c0 (LWP 22478)' Thread 1 (which is the one gdb chooses when you attach), shows a backtrace of: (gdb) bt #0 __unregister_atfork (dso_handle=) at ../nptl/sysdeps/unix/sysv/linux/unregister-atfork.c:117 #1 0x7f5174fe8716 in __do_global_dtors_aux () from /lib/x86_64-linux-gnu/libnss_ldap.so.2 #2 0x7a9b0430 in ?? () #3 0x7a9b0600 in ?? () #4 0x7f5174ff5371 in _fini () from /lib/x86_64-linux-gnu/libnss_ldap.so.2 #5 0x002c in ?? () #6 0x7f517780992d in _dl_fini () at dl-fini.c:259 Backtrace stopped: previous frame inner to this frame (corrupt stack?) Thread 2 shows a backtrace of: (gdb) bt #0 0x7f517675e89c in __lll_lock_wait () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x7f517675a065 in _L_lock_858 () from /lib/x86_64-linux-gnu/libpthread.so.0 #2 0x7f5176759eba in pthread_mutex_lock () from /lib/x86_64-linux-gnu/libpthread.so.0 #3 0x7f5174feab78 in _nss_ldap_enter () at ldap-nss.c:597 #4 0x7f5176c680c5 in __libc_fork () at ../nptl/sysdeps/unix/sysv/linux/x86_64/../fork.c:96 #5 0x7f517758a249 in fork_exec_with_pipes (intermediate_child=0, working_directory=0x0, argv=0x7f516c004830, envp=0x0, close_descriptors=1, search_path=1, stdout_to_null=0, stderr_to_null=0, child_inherits_stdin=0, file_and_argv_zero=0, child_setup=0, user_data=0x0, child_pid=0x7f51717b4a68, standard_input=0x0, standard_output=0x7f51717b4a60, standard_error=0x7f51717b4a64, error=0x7f51717b4ba8) at /build/buildd/glib2.0-2.32.0/./glib/gspawn.c:1232 #6 0x7f517758aa44 in g_spawn_sync (working_directory=, argv=, envp=, flags=, child_setup=, user_data=0x0, standard_output=0x7f51717b4b38, standard_error=0x7f51717b4b40, exit_status=0x7f51717b4b4c, error=0x7f51717b4ba8) at /build/buildd/glib2.0-2.32.0/./glib/gspawn.c:285 #7 0x7f517758b149 in g_spawn_command_line_sync (command_line=, standard_output=0x7f51717b4b38, standard_error=0x7f51717b4b40, exit_status=0x7f51717b4b4c, error=0x7f51717b4ba8) at /build/buildd/glib2.0-2.32.0/./glib/gspawn.c:722 #8 0x7f5177013629 in get_session_address_dbus_launch (error=0x7f51717b4ba8) at /build/buildd/glib2.0-2.32.0/./gio/gdbusaddress.c:1052 #9 0x7f517701507a in get_session_address_platform_specific (error=0x7f51717b4ba8) at /build/buildd/glib2.0-2.32.0/./gio/gdbusaddress.c:1149 #10 g_dbus_address_get_for_bus_sync (bus_type=G_BUS_TYPE_SESSION, cancellable=, error=0x7f51717b4c88) at /build/buildd/glib2.0-2.32.0/./gio/gdbusaddress.c:1232 #11 0x7f517701de4e in get_uninitialized_connection (bus_type=G_BUS_TYPE_SESSION, cancellable=0x0, error=0x7f51717b4c88) at /build/buildd/glib2.0-2.32.0/./gio/gdbusconnection.c:6750 #12 0x7f517702535b in g_bus_get_sync (bus_type=, cancellable=0x0, error=0x7f51717b4c88) at /build/buildd/glib2.0-2.32.0/./gio/gdbusconnection.c:6807 #13 0x7f5175416caa in dconf_settings_backend_send (dcsb=0x112b010, dcem=0x7f51717b4cd0, callback=0x7f5175417570 , user_data=0x11174e0) at dconfsettingsbackend.c:144 #14 0x7f5175417087 in dconf_settings_backend_subscribe_context_func (data=0x11174e0) at dconfsettingsbackend.c:612 #15 0x7f517754cc9a in g_main_dispatch (context=0x112b800) at /build/buildd/glib2.0-2.32.0/./glib/gmain.c:2515 #16 g_main_context_dispatch (context=0x112b800) at /build/buildd/glib2.0-2.32.0/./glib/gmain.c:3052 #17 0x7f517754d060 in g_main_context_iterate (dispatch=1, block=, context=0x112b800, self=) at /build/buildd/glib2.0-2.32.0/./glib/gmain.c:3123 #18 g_main_context_iterate (context=0x112b800, block=, dispatch=1, self=) at /build/buildd/glib2.0-2.32.0/./glib/gmain.c:3060 #19 0x7f517754d45a in g_main_loop_run (loop=0x7f516c0010c0) at /b
