Bug#1015007: epiphany-browser: Hangs if started by normal user, but works if started by root
Package: epiphany-browser Version: 42.3-1 Severity: important Dear Maintainer, I installed epiphany-browser from repo as normal but it just won't show a page after firing up. I start it from a terminal and it reports: bwrap: Can't find source path /root/.cache/at-spi/bus_0.0: Permission denied browser window never shows up even I saw it from my panel (xfce4-panel) and it has been started, Ctrl-C in terminal won't kill it and I have to kill -9. Saw the message above, I try launching it with sudo, which leads to a working browser window. -- System Information: Debian Release: sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.18.0-9.1-liquorix-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages epiphany-browser depends on: ii dbus-user-session [default-dbus-session-bus] 1.14.0-1 ii dbus-x11 [dbus-session-bus] 1.14.0-1 ii epiphany-browser-data 42.3-1 ii gsettings-desktop-schemas 42.0-1 ii iso-codes 4.10.0-1 ii libarchive13 3.6.0-1 ii libatk1.0-0 2.38.0-1 ii libc6 2.33-8 ii libcairo2 1.16.0-6 ii libdazzle-1.0-0 3.44.0-1 ii libgcr-base-3-1 3.41.0-4 ii libgcr-ui-3-1 3.41.0-4 ii libgdk-pixbuf-2.0-0 2.42.8+dfsg-1 ii libglib2.0-0 2.72.3-1 ii libgmp10 2:6.2.1+dfsg1-1 ii libgtk-3-03.24.34-1 ii libhandy-1-0 1.6.2-1 ii libhogweed6 3.7.3-1 ii libjavascriptcoregtk-4.1-02.36.4-1 ii libjson-glib-1.0-01.6.6-1 ii libnettle83.7.3-1 ii libpango-1.0-01.50.7+ds-1 ii libsecret-1-0 0.20.5-2 ii libsoup-3.0-0 3.0.7-1 ii libsqlite3-0 3.39.0-2 ii libwebkit2gtk-4.1-0 2.36.4-1 ii libxml2 2.9.14+dfsg-1 Versions of packages epiphany-browser recommends: ii ca-certificates 20211016 pn evince ii yelp 42.1-2 epiphany-browser suggests no packages. -- no debconf information
Bug#959223: fcitx won't start anymore
Package: fcitx Version: 4.2.9.7-3 Severity: serious Dear Maintainer, I don't think I've done anything fcitx- or input-method-related, but fcitx just won't start after a normal reboot. I tried issuing fcitx command in a terminal but fcitx didn't show up either. Here is the output from fcitx-diagnose:https://cfp.vim-cn.com/cbhQ3
Bug#934105: another backtrace
> > could it be that the crashes started occurring after a glib update? > Sorry for the late reply. It's hard to say as it's been like this for some time as I've mentioned in the original report. But since xfce 4.14 is coming and so I am thinking about testing after sid upgrade to newer version of xfce4. And I've noticed indeed that after upgrade to xfce 4.14 and the crash and core dumps never happened anymore. I am thinking it''s time to close this bug report for now. I'll keep an eye on this and in case it happens again, may god help me it won't, I'll file a new report. Regards, Jun
Bug#934105: another backtrace
So during a upgrade this morning this happened again: $ coredumpctl list TIMEPID UID GID SIG COREFILE EXE Sun 2019-08-11 08:33:45 CST1044 1000 1000 11 present /usr/bin/xfdesktop Sun 2019-08-11 08:33:45 CST 32695 1000 1000 11 present /usr/bin/xfce4-appfinder Sun 2019-08-11 08:33:45 CST1040 1000 1000 11 present /usr/bin/xfce4-panel Sun 2019-08-11 08:34:49 CST6557 1000 1000 11 present /usr/bin/xfdesktop Sun 2019-08-11 08:35:10 CST6836 1000 1000 11 present /usr/bin/xfdesktop $ coredumpctl info 6557 PID: 6557 (xfdesktop) UID: 1000 (adam) GID: 1000 (adam) Signal: 11 (SEGV) Timestamp: Sun 2019-08-11 08:34:48 CST (13s ago) Command Line: xfdesktop --display :0.0 --sm-client-id 22a396536-a119-4d09-8614-8656bfafc117 Executable: /usr/bin/xfdesktop Control Group: /user.slice/user-1000.slice/session-2.scope Unit: session-2.scope Slice: user-1000.slice Session: 2 Owner UID: 1000 (adam) Boot ID: fe9a729066a445b8a9b18c1d08fc80f6 Machine ID: 647a0bfe1e794d9db74e8b9202aab665 Hostname: MyDebian Storage: /var/lib/systemd/coredump/core.xfdesktop.1000.fe9a729066a445b8a9b18c1d08fc80f6.6557.156548368800 .l Message: Process 6557 (xfdesktop) of user 1000 dumped core. Stack trace of thread 6558: #0 0x7f9cafce975a g_slice_alloc (libglib-2.0.so.0) #1 0x7f9cafcee183 g_string_sized_new (libglib-2.0.so.0) #2 0x7f9cafcb5de1 n/a (libglib-2.0.so.0) #3 0x7f9cafcb72c5 g_build_filename (libglib-2.0.so.0) #4 0x7f9caff9e9f8 n/a (libgio-2.0.so.0) #5 0x7f9caffa48fa n/a (libgio-2.0.so.0) #6 0x7f9caffa5479 g_file_monitor_source_handle_event (libgio-2.0.so.0) #7 0x7f9caffb0559 n/a (libgio-2.0.so.0) #8 0x7f9caffafadc n/a (libgio-2.0.so.0) #9 0x7f9caffafc96 n/a (libgio-2.0.so.0) #10 0x7f9caffaefe9 n/a (libgio-2.0.so.0) #11 0x7f9cafccb898 g_main_context_dispatch (libglib-2.0.so.0) #12 0x7f9cafccbc88 n/a (libglib-2.0.so.0) #13 0x7f9cafccbd1c g_main_context_iteration (libglib-2.0.so.0) #14 0x7f9cafccbd61 n/a (libglib-2.0.so.0) #15 0x7f9cafcf489d n/a (libglib-2.0.so.0) #16 0x7f9cafc63fa3 start_thread (libpthread.so.0) #17 0x7f9cafb944cf __clone (libc.so.6) Stack trace of thread 6557: #0 0x7f9cafb89819 __GI___poll (libc.so.6) #1 0x7f9cafccbbf6 n/a (libglib-2.0.so.0) #2 0x7f9cafccbf82 g_main_loop_run (libglib-2.0.so.0) #3 0x7f9cb05fd8e7 gtk_main (libgtk-x11-2.0.so.0) #4 0x55de8878bc6c n/a (xfdesktop) #5 0x55de8878c0a6 n/a (xfdesktop) #6 0x7f9cafcc8263 n/a (libglib-2.0.so.0) #7 0x7f9cafcc8c9e n/a (libglib-2.0.so.0) #8 0x7f9cafccb928 g_main_context_dispatch (libglib-2.0.so.0) #9 0x7f9cafccbc88 n/a (libglib-2.0.so.0) #10 0x7f9cafccbd1c g_main_context_iteration (libglib-2.0.so.0) #11 0x7f9caff4ca0d g_application_run (libgio-2.0.so.0) #12 0x55de88780fad main (xfdesktop) #13 0x7f9cafabf09b __libc_start_main (libc.so.6) #14 0x55de88780fea _start (xfdesktop) Stack trace of thread 6559: #0 0x7f9cafb89819 __GI___poll (libc.so.6) #1 0x7f9cafccbbf6 n/a (libglib-2.0.so.0) #2 0x7f9cafccbf82 g_main_loop_run (libglib-2.0.so.0) #3 0x7f9caff86e46 n/a (libgio-2.0.so.0) #4 0x7f9cafcf489d n/a (libglib-2.0.so.0) #5 0x7f9cafc63fa3 start_thread (libpthread.so.0) #6 0x7f9cafb944cf __clone (libc.so.6) I then installed libglib2.0-0-dbgsym libgtk2.0-0-dbgsym libc6-dbg xfdesktop4-dbgsym and did a backtrace: (gdb) #0 0x7f9cafce975a in magazine_chain_pop_head (magazine_chunks=0x7f9ca8000bf0) at ../../../glib/gslice.c:538 #1 0x7f9cafce975a in thread_memory_magazine1_alloc (tmem=0x7f9ca8000bd0, ix=1) at ../../../glib/gslice.c:841 #2 0x7f9cafce975a in g_slice_alloc (mem_size=mem_size@entry=24) at ../../../glib/gslice.c:1015 #3 0x7f9cafcee183 in g_string_sized_new (dfl_size=dfl_size@entry=2) at ../../../glib/gstring.c:121 #4 0x7f9cafcee6b4 in g_string_new (init=init@entry=0x0) at ../../../glib/gstring.c:148 #5 0x7f9cafcb5de1 in g_build_path_va (separator=separator@entry=0x7f9cafd1af0d "/", first_element=first_element@entry=0x55de896553d0 "/usr/share/applications", args=args@entry=0x7f9cacf65720, str_array=str_a
Bug#934105: xfdesktop4: xfdesktop crashes and coredump when upgrading
Thanks again Bernhard! > As I could not get it crashing by just doing upgrades, I tried to > inspect a running process and got into a source file named "screen.c" > and functions related to screen resolution. Then I tried to change > resolution and the xfdesktop got into a similar backtrace still without > crashing. Therefore I asked if your processes would crash, if you > try changing the resolution. > No, I don't think it had anything to do with changing resolution. I tried changing my original resolution to several others, 1680*1050, 1600*1024 and 1400*1050, none of them caused a coredump. > > I found a similar report was reported by another user in > https://bugs.debian.org/933202 > Seems like what I am experincing. I'll keep an eye on it. Kind regards, Jun
Bug#934105: xfdesktop4: xfdesktop crashes and coredump when upgrading
Thank you Bernhard!
I was mentioning google-chrome-stable just to make it clear that I was not
upgrading any xfce4 desktop related packages when the crash happened, not
that it had anything to do with the crash.
As for for question at the end about changing display resolution, I don't
follow you. Pardon me if I am misunderstanding, are you asking whether I
changed screen resolution when it happened? If that's what you mean, then
no, I haven't change my screen resolution since I don't even remember when.
Also, before, during or after the crash, screen resolution remained fine.
In fact, all opened windows were fine except wallpaper and xfce4-panel
disappeared and appeared again as I mentioned.
Anyway, I managed to get the backtrace output:
#0 0x7fc31ce4975a in magazine_chain_pop_head
(magazine_chunks=0x55a6673027e0) at ../../../glib/gslice.c:538
#1 0x7fc31ce4975a in thread_memory_magazine1_alloc (tmem=0x55a6673027c0,
ix=1) at ../../../glib/gslice.c:841
#2 0x7fc31ce4975a in g_slice_alloc (mem_size=mem_size@entry=24) at
../../../glib/gslice.c:1015
#3 0x7fc31ce27316 in g_list_prepend (list=list@entry=0x55a66745dd50 =
{...}, data=data@entry=0x55a66741fa20)
at ../../../glib/glist.c:314
#4 0x7fc31daf4b87 in update_client_list (screen=0x55a6673f78a0 [
WnckScreen]) at screen.c:1637
#5 0x7fc31daf4b87 in do_update_now (screen=0x55a6673f78a0 [WnckScreen])
at screen.c:2332
#6 0x7fc31daf5b44 in update_idle (data=) at
screen.c:2355
#7 0x7fc31ce2b898 in g_main_dispatch (context=0x55a66731e690) at
../../../glib/gmain.c:3189
#8 0x7fc31ce2b898 in g_main_context_dispatch
(context=context@entry=0x55a66731e690)
at ../../../glib/gmain.c:3854
#9 0x7fc31ce2bc88 in g_main_context_iterate
(context=0x55a66731e690, block=block@entry=1, dispatch=dispatch@entry=1,
self=)
at ../../../glib/gmain.c:3927
#10 0x7fc31ce2bf82 in g_main_loop_run (loop=0x55a6673fb780) at
../../../glib/gmain.c:4123
#11 0x7fc31d75d8e7 in IA__gtk_main () at ./gtk/gtkmain.c:1270
#12 0x55a665e6fc6c in xfdesktop_application_start (app=0x55a66731a150 [
XfdesktopApplication])
at xfdesktop-application.c:768
#13 0x55a665e700a6 in cb_wait_for_window_manager_destroyed
(data=0x7fc30c007b60) at xfdesktop-application.c:630
#14 0x7fc31ce28263 in g_source_callback_unref (cb_data=0x55a667366d50)
at ../../../glib/gmain.c:1553
#15 0x7fc31ce28263 in g_source_callback_unref (cb_data=0x55a667366d50)
at ../../../glib/gmain.c:1546
#16 0x7fc31ce28c9e in g_source_destroy_internal (source=0x55a66737b2c0,
context=0x55a66731e690, have_lock=1)
at ../../../glib/gmain.c:1238
#17 0x7fc31ce2b928 in g_main_dispatch (context=0x55a66731e690) at
../../../glib/gmain.c:3213
#18 0x7fc31ce2b928 in g_main_context_dispatch
(context=context@entry=0x55a66731e690)
at ../../../glib/gmain.c:3854
#19 0x7fc31ce2bc88 in g_main_context_iterate
(context=context@entry=0x55a66731e690, block=block@entry=1,
dispatch=dispatch@entry=1, self=)
at ../../../glib/gmain.c:3927
#20 0x7fc31ce2bd1c in g_main_context_iteration
(context=context@entry=0x55a66731e690,
may_block=may_block@entry=1)
at ../../../glib/gmain.c:3988
#21 0x7fc31d0aca0d in g_application_run
(application=0x55a66731a150 [XfdesktopApplication], argc=, argv=0x7fff34b18268)
at ../../../gio/gapplication.c:2516
#22 0x55a665e64fad in main (argc=5, argv=0x7fff34b18268) at main.c:86
Regards,
Jiang Jun
Bug#906745: libreoffice-calc: LibreOffice-Calc takes all available memory and freezes system when open a file
Sorry I ,accidentally replied to your personal email only. >From the last few day's experience, the problem seems to be gone. Thanks for your help. Rene Engelhard 于 2018年8月24日周五 18:41写道： > [ please keep bugs in Cc to discussions are recorded. ] > > Hi, > > On Tue, Aug 21, 2018 at 10:25:36AM +0800, Jun Jiang wrote: > >I've fixed it and now all dependencies are marked "ii" and both > >libreoffice and libreoffice-core are shown as "APT-Manual-Installed: > yes" > >in the ouput of apt show. I'll examine whether libreoffice behaves at > >current status and will report if the problem persists. > > Ping? :) And? :) > > Regards, > > Rene >
Bug#904544: gimp failed to launch from menu entry or terminal command
On Thu, 9 Aug 2018 11:28:23 +0100 Simon McVittie wrote: > On Wed, 25 Jul 2018 at 11:12:52 +0800, Jiang Jun wrote: > > When I click GIMP launcher from menu entry, nothing happens. > ... > > Versions of packages gimp depends on: > ... > > ii libbabl-0.1-01:0.1.54-dmo1 > ... > > ii libgegl-0.4-01:0.4.6-dmo1 > ... > > ii libmypaint-1.3-0 1:1.3.0-dmo6 > > You seem to have installed unofficial packages from deb-multimedia.org, > with artificially higher versions than the versions from Debian. We > cannot support systems with unoffical packages installed. Please install > gimp's dependencies from Debian and try again. > > If this bug still exists without using deb-multimedia.org packages, > please reply describing steps to reproduce the bug and the new symptoms, > and include the package information from "reportbug --template gimp" so > that we know which package versions you have installed. > > Thanks, > smcv > > I didn't thought it was the same thing, but as I went through the GIMP bug list I saw James Van Zandt mentioned in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903514: "Specifically: sudo apt-get install libopenblas-base- libopenblas-dev- \ libblas3 liblapack3 libblas-dev liblapack-dev Unfortunately julia and libjulia0.6 were also removed here, since they depend on libopenblas-base. I intend to report this as a bug, and request that they depend instead on the virtual packages libblas.so.3 and liblapack.so.3 (which can also be provided by liblapack3 and libblas3, resp.)." And that solved my problem too. In my case, libopenblas-dev:amd64 (0.3.2+ds-1) and libopenblas-base:amd64 (0.3.2+ds-1) got removed and after that, GIMP launched successsfully just like it used to do. Hope it helps.
