[Bug 1841024] Re: sreen captured
It sounds like your PrtSc (print screen) key might be getting stuck. Please try tapping it a few times to unstick it, or using something flat to lever it back up. ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1841024 Title: sreen captured To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1841024/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1841024] [NEW] sreen captured
You have been subscribed to a public bug: The system begins to make screen captures without stopping, making it impossible to use to the point of crashing the system and making a stressful noise. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-25.26~18.04.1-generic 5.0.18 Uname: Linux 5.0.0-25-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Aug 22 01:36:22 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Elitegroup Computer Systems Mobile 4 Series Chipset Integrated Graphics Controller [1019:995b] Subsystem: Elitegroup Computer Systems Mobile 4 Series Chipset Integrated Graphics Controller [1019:995b] MachineType: Semp Toshiba IS 1414 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-25-generic root=UUID=fbbaea76-1d2d-4b24-850f-cb5685d71e24 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/07/2010 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: MTVNCRB01.86C..X.00 dmi.board.name: IS 1414 dmi.board.vendor: Semp Toshiba dmi.board.version: CRB dmi.chassis.type: 10 dmi.chassis.vendor: Semp Toshiba dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrMTVNCRB01.86C..X.00:bd05/07/2010:svnSempToshiba:pnIS1414:pvr20ga:rvnSempToshiba:rnIS1414:rvrCRB:cvnSempToshiba:ct10:cvr: dmi.product.name: IS 1414 dmi.product.version: 20ga & ICH9M Chipset dmi.sys.vendor: Semp Toshiba version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug bionic corruption ubuntu -- sreen captured https://bugs.launchpad.net/bugs/1841024 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1840557] Re: [Dell Inspiron 7559] Battery of 66% shows full icon on 19.04
** Summary changed: - Battery indicator at 66% show full icon on 19.04 + [Dell Inspiron 7559] Battery of 66% shows full icon on 19.04 ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1840557 Title: [Dell Inspiron 7559] Battery of 66% shows full icon on 19.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1840557/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1840996] Re: Working with smb
Add: https://gitlab.gnome.org/GNOME/nautilus/issues/1201 ** Information type changed from Private to Public ** Description changed: + https://gitlab.gnome.org/GNOME/nautilus/issues/1201 + + --- + I opened nautilus, accessed a shared resource with samba. Then I tried to write in that mounted folder. And he threw me that he had no writing privileges. I went to the samba server configuration and increased the privileges. And I tried to write *without* closing nautilus. It was something similar to what I mention. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: nautilus 1:3.33.90-1ubuntu1 Uname: Linux 5.2.9-050209-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 21 19:25:59 2019 ExecutablePath: /usr/bin/nautilus ExecutableTimestamp: 1565361020 GsettingsChanges: b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2018-12-02 (262 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/nautilus --gapplication-service ProcCwd: /home/caravena ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=es_CL:es LANG=es_CL.UTF-8 Signal: 6 SourcePackage: nautilus UpgradeStatus: Upgraded to eoan on 2018-12-02 (262 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo usr_lib_nautilus: ** Bug watch added: gitlab.gnome.org/GNOME/nautilus/issues #1201 https://gitlab.gnome.org/GNOME/nautilus/issues/1201 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1840996 Title: Working with smb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1840996/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1840975] Re: Gimp 2.10.12 crash - deleted an empty transparent layer
Thank you for reporting this bug. However, this was not filed using the
"ubuntu-bug" tool, therefore this bug does not contain any hints about
hardware, or any
other necessary information. Therefore, this bug is invalid. Please
report bugs by opening a terminal and typing "ubuntu-bug {packagename}"
in the future.
If this was reported via any process requested by the GIMP developers,
please report the bug upstream at gimp.org, not here. Again, thank you.
** Changed in: gimp (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gimp in Ubuntu.
https://bugs.launchpad.net/bugs/1840975
Title:
Gimp 2.10.12 crash - deleted an empty transparent layer
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1840975/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1840975] [NEW] Gimp 2.10.12 crash - deleted an empty transparent layer
Public bug reported:
Ubuntu Studio 19.04
Gimp 2.10.12
Pasted an image (675 x 799) into Gimp
Added transparent layer
Duplicated image
Deleted transparent layer
Gimp crashed
```
GNU Image Manipulation Program version 2.10.12
git-describe: GIMP_2_10_10-209-g3d8535b55f
C compiler:
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/8/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu
8.3.0-6ubuntu1' --with-bugurl=file:///usr/share/doc/gcc-8/README.Bugs
--enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++ --prefix=/usr
--with-gcc-major-version-only --program-suffix=-8
--program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix
--libdir=/usr/lib --enable-nls --enable-bootstrap --enable-clocale=gnu
--enable-libstdcxx-debug --enable-libstdcxx-time=yes
--with-default-libstdcxx-abi=new --enable-gnu-unique-object
--disable-vtable-verify --enable-libmpx --enable-plugin --enable-default-pie
--with-system-zlib --with-target-system-zlib --enable-objc-gc=auto
--enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64
--with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic
--enable-offload-targets=nvptx-none --without-cuda-driver
--enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu
--target=x86_64-linux-gnu
Thread model: posix
gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1)
using GEGL version 0.4.16 (compiled against version 0.4.16)
using GLib version 2.60.4 (compiled against version 2.60.0)
using GdkPixbuf version 2.38.1 (compiled against version 2.38.1)
using GTK+ version 2.24.32 (compiled against version 2.24.32)
using Pango version 1.42.3 (compiled against version 1.42.3)
using Fontconfig version 2.13.1 (compiled against version 2.13.1)
using Cairo version 1.16.0 (compiled against version 1.16.0)
```
> fatal error: Aborted
Stack trace:
```
# Stack traces obtained from PID 4431 - Thread 4431 #
[New LWP 4432]
[New LWP 4433]
[New LWP 4434]
[New LWP 4436]
[New LWP 4587]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
__libc_read (nbytes=256, buf=0x7fff858ed050, fd=15) at
../sysdeps/unix/sysv/linux/read.c:26
Id Target Id Frame
* 1Thread 0x7fc0442dde00 (LWP 4431) "gimp-2.10" __libc_read (nbytes=256,
buf=0x7fff858ed050, fd=15) at ../sysdeps/unix/sysv/linux/read.c:26
2Thread 0x7fc043b1d700 (LWP 4432) "worker" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
3Thread 0x7fc0416cd700 (LWP 4433) "gmain" 0x7fc045fc7729 in
__GI___poll (fds=0x7fc028001cd0, nfds=2, timeout=-1) at
../sysdeps/unix/sysv/linux/poll.c:29
4Thread 0x7fc0408e0700 (LWP 4434) "gdbus" 0x7fc045fc7729 in
__GI___poll (fds=0x55a6d9e2c330, nfds=2, timeout=-1) at
../sysdeps/unix/sysv/linux/poll.c:29
5Thread 0x7fc02de9d700 (LWP 4436) "async" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
6Thread 0x7fbfd7fff700 (LWP 4587) "swap writer" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
Thread 6 (Thread 0x7fbfd7fff700 (LWP 4587)):
#0 0x7fc045fcd2e9 in syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
#1 0x7fc0462b193f in g_cond_wait () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x7fc0467570b9 in () at /usr/lib/x86_64-linux-gnu/libgegl-0.4.so.0
#3 0x7fc04628f87d in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4 0x7fc0460ac182 in start_thread (arg=) at
pthread_create.c:486
ret =
pd =
now =
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {140461939357440,
-2317528006440452510, 140735434126606, 140735434126607, 140735434126752,
140461939353856, 2353644763696660066, 2330314406011141730}, mask_was_saved =
0}}, priv = {pad = {0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0,
canceltype = 0}}}
not_first_call =
#5 0x7fc045fd3b1f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
Thread 5 (Thread 0x7fc02de9d700 (LWP 4436)):
#0 0x7fc045fcd2e9 in syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
#1 0x7fc0462b193f in g_cond_wait () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x55a6d95a38ac in ()
#3 0x7fc04628f87d in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4 0x7fc0460ac182 in start_thread (arg=) at
pthread_create.c:486
ret =
pd =
now =
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {140463380748032,
-2317528006440452510, 140735434135406, 140735434135407, 140735434135552,
14046338078, 2330093137656610402, 2330314406011141730}, mask_was_saved =
0}}, priv = {pad = {0x0, 0x0, 0x0, 0x0},
[Bug 1292041] Re: Lockscreen doesn't turn off the screen
Ubuntu 19.04 - xset dpms force off will turn monitors off, but somehow they wakeup in 10 seconds again. So not sure if this is a bug in screensaver, but it is a nasty and COSTLY bug. It will burn 100 watts (3 monitors) and lower lifetime of my monitors. What's the use of a screensaver or power mode, when it doesn't power off monitors. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1292041 Title: Lockscreen doesn't turn off the screen To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1292041/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1840955] [NEW] Evolution crashes on automatic mail check
Public bug reported: I set up Evolution to check my Exchange Web Services account every ten minutes. If I send a test e-mail to that address Evolution crashes whenever it regularly checks the mail. When it is restarted the new e-mail is sitting in the Inbox in Evolution. The only log output I have (no debug symbols installed) is: [1]4847 segmentation fault (core dumped) evolution ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: evolution 3.32.1-2 Uname: Linux 5.3.0-rc4-custom x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Aug 21 10:31:08 2019 InstallationDate: Installed on 2019-07-30 (21 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: evolution UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: evolution (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco evolution third-party-packages wayland-session -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1840955 Title: Evolution crashes on automatic mail check To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1840955/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1840947] Re: Erro fatal durante edição de arte
Thank you for reporting this bug. However, this was not filed using the
"ubuntu-bug" tool, therefore this bug does not contain any information
about the version of OS being used or any hints about hardware, or any
other necessary information. Therefore, this bug is invalid. Please
report bugs by opening a terminal and typing "ubuntu-bug {packagename}"
in the future.
If this was reported via any process requested by the GIMP developers,
please report the bug upstream at gimp.org, not here. Again, thank you.
** Changed in: gimp (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gimp in Ubuntu.
https://bugs.launchpad.net/bugs/1840947
Title:
Erro fatal durante edição de arte
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1840947/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1840947] [NEW] Erro fatal durante edição de arte
Public bug reported:
```
GNU Image Manipulation Program version 2.10.8
git-describe: GIMP_2_10_6-294-ga967e8d2c2
C compiler:
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/8/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu
8.2.0-13ubuntu1' --with-bugurl=file:///usr/share/doc/gcc-8/README.Bugs
--enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++ --prefix=/usr
--with-gcc-major-version-only --program-suffix=-8
--program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix
--libdir=/usr/lib --enable-nls --enable-clocale=gnu --enable-libstdcxx-debug
--enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new
--enable-gnu-unique-object --disable-vtable-verify --enable-libmpx
--enable-plugin --enable-default-pie --with-system-zlib
--with-target-system-zlib --enable-objc-gc=auto --enable-multiarch
--disable-werror --with-arch-32=i686 --with-abi=m64
--with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic
--enable-offload-targets=nvptx-none --without-cuda-driver
--enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu
--target=x86_64-linux-gnu
Thread model: posix
gcc version 8.2.0 (Ubuntu 8.2.0-13ubuntu1)
using GEGL version 0.4.14 (compiled against version 0.4.12)
using GLib version 2.60.4 (compiled against version 2.58.1)
using GdkPixbuf version 2.38.1 (compiled against version 2.38.0)
using GTK+ version 2.24.32 (compiled against version 2.24.32)
using Pango version 1.42.3 (compiled against version 1.42.3)
using Fontconfig version 2.13.1 (compiled against version 2.13.0)
using Cairo version 1.16.0 (compiled against version 1.16.0)
```
> fatal error: Abortado
Stack trace:
```
# Stack traces obtained from PID 12316 - Thread 12316 #
[New LWP 12319]
[New LWP 12320]
[New LWP 12321]
[New LWP 12322]
[New LWP 12323]
[New LWP 12324]
[New LWP 12325]
[New LWP 12326]
[New LWP 12327]
[New LWP 12348]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
__libc_read (nbytes=256, buf=0x7ffe6c92e950, fd=19) at
../sysdeps/unix/sysv/linux/read.c:26
Id Target Id Frame
* 1Thread 0x7ffbf9dd1e00 (LWP 12316) "gimp-2.10" __libc_read (nbytes=256,
buf=0x7ffe6c92e950, fd=19) at ../sysdeps/unix/sysv/linux/read.c:26
2Thread 0x7ffbf8d30700 (LWP 12319) "worker" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
3Thread 0x7ffbf852f700 (LWP 12320) "worker" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
4Thread 0x7ffbf7d2e700 (LWP 12321) "worker" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
5Thread 0x7ffbf565e700 (LWP 12322) "gmain" 0x7ffbfbabb729 in
__GI___poll (fds=0x5612f05e9920, nfds=2, timeout=-1) at
../sysdeps/unix/sysv/linux/poll.c:29
6Thread 0x7ffbf4e5d700 (LWP 12323) "gdbus" 0x7ffbfbabb729 in
__GI___poll (fds=0x5612f05fd440, nfds=3, timeout=-1) at
../sysdeps/unix/sysv/linux/poll.c:29
7Thread 0x7ffbd66c0700 (LWP 12324) "async" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
8Thread 0x7ffbd5ebf700 (LWP 12325) "worker" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
9Thread 0x7ffbcd6be700 (LWP 12326) "worker" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
10 Thread 0x7ffbd56be700 (LWP 12327) "worker" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
11 Thread 0x7ffbb6ffe700 (LWP 12348) "swap writer" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
Thread 11 (Thread 0x7ffbb6ffe700 (LWP 12348)):
#0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
No locals.
#1 0x7ffbfbda593f in g_cond_wait () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#2 0x7ffbfc24c799 in ?? () from /lib/x86_64-linux-gnu/libgegl-0.4.so.0
No symbol table info available.
#3 0x7ffbfbd8387d in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#4 0x7ffbfbba0182 in start_thread (arg=) at
pthread_create.c:486
ret =
pd =
now =
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {140719083742976,
-7803347054893772418, 140730719984366, 140730719984367, 140730719984512,
140719083739392, 7801251384849289598, 7801085879663677822}, mask_was_saved =
0}}, priv = {pad = {0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0,
canceltype = 0}}}
not_first_call =
#5 0x7ffbfbac7b1f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
No locals.
Thread 10 (Thread 0x7ffbd56be700 (LWP 12327)):
#0 syscall () at
[Bug 1806257] Re: gnome-shell excessive logging cannot bind to x11-unix
gnome-shell's failure to bind can also be caused by namespace.conf settings, currently gdm/gnome-shell etc do not take this into account, breaking gdm which worked fine without wayland. https://manpages.ubuntu.com/manpages/trusty/man5/namespace.conf.5.html Now, if you have in that file: /tmp/tmp/tmp-inst/ userroot,adm gdm etc write their files to /tmp/.X0-lock /tmp/.X11-unix/ and so on, but gnome-shell tries to open the files at /tmp/tmp-inst/luser/.X11-unix/ (after private namespaces have been polyinstantiated). -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1806257 Title: gnome-shell excessive logging cannot bind to x11-unix To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1806257/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1840557] Re: Battery indicator at 66% show full icon on 19.04
DELL Inspiron 7559 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1840557 Title: Battery indicator at 66% show full icon on 19.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1840557/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1840557] Re: Battery indicator at 66% show full icon on 19.04
** Attachment added: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1840557/+attachment/5283736/+files/dmesg.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1840557 Title: Battery indicator at 66% show full icon on 19.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1840557/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1766230] Re: Strange window matching behaviour between Slack and Chrome
For reference, I also see this same issue with Firefox set as my default browser, and I am using the snap version of Slack. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1766230 Title: Strange window matching behaviour between Slack and Chrome To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1766230/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1766230] Re: Strange window matching behaviour between Slack and Chrome
Seeing this behavior, as well. Others reference vscode (in the comment above), so I am curious to know if this is related to electron, or if this is a snap-specific issue. I do see reference to it as a snap-specific issue here: https://forum.snapcraft.io/t/slack-opening-file-browser-firefox-and- chrome-in-the-snaps-context/8969/3 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1766230 Title: Strange window matching behaviour between Slack and Chrome To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1766230/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1840921] Re: totem crashed with SIGABRT
*** This bug is a duplicate of bug 1501049 *** https://bugs.launchpad.net/bugs/1501049 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 #1501049, 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/1840921/+attachment/5283712/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1840921/+attachment/5283714/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1840921/+attachment/5283720/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1840921/+attachment/5283721/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1840921/+attachment/5283722/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1840921/+attachment/5283723/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1840921/+attachment/5283724/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1501049 totem crashed with assertion failure [Totem:ERROR:totem-grilo.c:729:browse_cb: code should not be reached] ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1840921 Title: totem crashed with SIGABRT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1840921/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 641182] Re: photo viewer always opens maximized
Ubuntu 10.10 (maverick) reached end-of-life on April 10, 2012. This release of Ubuntu is no longer receiving maintenance updates. If this is still an issue using a maintained version of Ubuntu please let us know. Paul White [Ubuntu Bug Squad] ** Changed in: hundredpapercuts Status: New => Incomplete ** Changed in: shotwell (Ubuntu) Status: Triaged => Incomplete ** Changed in: shotwell Importance: Unknown => Undecided ** Changed in: shotwell Remote watch: redmine.yorba.org #2569 => None ** Changed in: shotwell Status: New => Incomplete ** Changed in: hundredpapercuts Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shotwell in Ubuntu. https://bugs.launchpad.net/bugs/641182 Title: photo viewer always opens maximized To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/641182/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 864494] Re: Wrong preview image in the file open dialog.
** Changed in: hundredpapercuts Status: Triaged => Fix Released ** Changed in: gtk+3.0 (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/864494 Title: Wrong preview image in the file open dialog. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/864494/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1029932] Re: Brightness and Volume laptop keys behave inconsistently
Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017. This release of Ubuntu is no longer receiving maintenance updates. If this is still an issue using a maintained version of Ubuntu please let us know. Paul White [Ubuntu Bug Squad] ** Changed in: hundredpapercuts Status: Confirmed => Incomplete ** Changed in: gnome-power-manager (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1029932 Title: Brightness and Volume laptop keys behave inconsistently To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1029932/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1380561] Re: "Unknown variable 'ansA'" when editing the result after converting to hexadecimal
** Bug watch added: gitlab.gnome.org/GNOME/gnome-calculator/issues #39 https://gitlab.gnome.org/GNOME/gnome-calculator/issues/39 ** Changed in: gnome-calculator Importance: Medium => Unknown ** Changed in: gnome-calculator Status: Expired => Unknown ** Changed in: gnome-calculator Remote watch: GNOME Bug Tracker #748731 => gitlab.gnome.org/GNOME/gnome-calculator/issues #39 ** Changed in: hundredpapercuts Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-calculator in Ubuntu. https://bugs.launchpad.net/bugs/1380561 Title: "Unknown variable 'ansA'" when editing the result after converting to hexadecimal To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-calculator/+bug/1380561/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1288182] Re: Cyrillic not displayed in the input field
The same problem reproduced with displaying PDF form in fresh Firefox and Chrome web browsers, that use JS rendering. So the problem is in PDF document - PDF document doesn't embed non-Cyrillic font letters in PDF file. For this cases is better to display symbols via some default font, instead of missing letters. So can we add workaround for "warning: layout text: cannot convert U+65E5" - replace font for this symbol to system default? https://www.socialmediagossips.com/ -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1288182 Title: Cyrillic not displayed in the input field To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/1288182/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1840900] [NEW] Gnome-shell-extension-ubuntu-dock not run in the absence of a display
Public bug reported: Ubuntu 18.04.3, GeForce GTX 750, Nvidia proprietary driver v390 gnome-shell-extension-ubuntu-dock - 0.9.1ubuntu18.04.3 I need the graphical environment to start without a monitor. This is necessary for testing applications. For this, I have created a configuration /usr/share/X11/xorg.conf.d/10-nvidia.conf: Section "Monitor" Identifier "Configured Monitor" HorizSync 5.0 - 1000.0 VertRefresh 5.0 - 200.0 ModeLine "1920x1080" 148.50 1920 2448 2492 2640 1080 1084 1089 1125 +Hsync +Vsync EndSection Section "OutputClass" Identifier "nvidia" MatchDriver "nvidia-drm" Driver "nvidia" Option "AllowEmptyInitialConfiguration" ModulePath "/usr/lib/x86_64-linux-gnu/nvidia/xorg" EndSection Section "Device" Identifier "Idek Iiyama" Option "ConnectedMonitor" "DFP-0" EndSection If I turn off and turn on the computer without a connected display, then I will get a standard Gnome3 without ubuntu-dock When booting the system, I get an error: Aug 21 11:22:51 box gnome-shell[3417]: JS WARNING: [resource:///org/gnome/shell/ui/workspaceThumbnail.js 891]: reference to undefined property "_switchWorkspaceNotifyId" Aug 21 11:22:51 box gnome-shell[3417]: JS WARNING: [/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js 1778]: reference to undefined property "_workspaceIsolation" Aug 21 11:22:51 box gnome-shell[3417]: JS ERROR: TypeError: this._workspaceIsolation is undefined#012DockManager<._deleteDocks@/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:1778:9#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012DockManager<._toggle@/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:1662:9#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22 Aug 21 11:22:51 box gnome-shell[3417]: JS ERROR: TypeError: this._workspaceIsolation is undefined#012DockManager<._deleteDocks@/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:1778:9#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012DockManager<._toggle@/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:1662:9#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell-extension-ubuntu-dock 0.9.1ubuntu18.04.3 ProcVersionSignature: Ubuntu 5.0.0-25.26~18.04.1-generic 5.0.18 Uname: Linux 5.0.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 Date: Wed Aug 21 12:35:20 2019 InstallationDate: Installed on 2019-05-06 (106 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "2.png" https://bugs.launchpad.net/bugs/1840900/+attachment/5283659/+files/2.png ** Description changed: Ubuntu 18.04.3, GeForce GTX 750, Nvidia proprietary driver v390 gnome-shell-extension-ubuntu-dock - 0.9.1ubuntu18.04.3 I need the graphical environment to start without a monitor. This is necessary for testing applications. - For this, I have created a configuration /usr/share/X11/xorg.conf.d/10-nvidia.conf - ``` + For this, I have created a configuration + /usr/share/X11/xorg.conf.d/10-nvidia.conf: + Section "Monitor" - Identifier "Configured Monitor" - HorizSync 5.0 - 1000.0 - VertRefresh 5.0 - 200.0 - ModeLine "1920x1080" 148.50 1920 2448 2492 2640 1080 1084 1089 1125 +Hsync +Vsync + Identifier "Configured Monitor" + HorizSync 5.0 - 1000.0 + VertRefresh 5.0 - 200.0 + ModeLine "1920x1080" 148.50 1920 2448 2492 2640 1080 1084 1089 1125 +Hsync +Vsync EndSection Section "OutputClass" - Identifier "nvidia" - MatchDriver "nvidia-drm" - Driver "nvidia" - Option "AllowEmptyInitialConfiguration" - ModulePath "/usr/lib/x86_64-linux-gnu/nvidia/xorg" + Identifier "nvidia" + MatchDriver "nvidia-drm" + Driver "nvidia" + Option "AllowEmptyInitialConfiguration" + ModulePath "/usr/lib/x86_64-linux-gnu/nvidia/xorg" EndSection Section "Device" - Identifier "Idek Iiyama" - Option "ConnectedMonitor" "DFP-0" + Identifier "Idek Iiyama" + Option "ConnectedMonitor" "DFP-0" EndSection - ``` - If I turn off and turn on the computer without a connected display, then - I will get a standard Gnome3 without ubuntu-dock + + If I turn off and turn on the computer without a connected display, then I will get a standard Gnome3 without ubuntu-dock When booting the system, I get an error: - ``` + Aug 21 11:22:51 box gnome-shell[3417]: JS WARNING: [resource:///org/gnome/shell/ui/workspaceThumbnail.js 891]: reference to undefined property
[Bug 576751] Re: wnck-applet has memory leak
** Changed in: gnome-panel (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in Ubuntu. https://bugs.launchpad.net/bugs/576751 Title: wnck-applet has memory leak To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-panel/+bug/576751/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 551052] Re: wnck-applet crashed with SIGSEGV in cairo_translate()
** Changed in: libwnck (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libwnck in Ubuntu. https://bugs.launchpad.net/bugs/551052 Title: wnck-applet crashed with SIGSEGV in cairo_translate() To manage notifications about this bug go to: https://bugs.launchpad.net/libwnck/+bug/551052/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1822351] Re: Nautilus does not open after updating to 19.04
Hi, in case that helps, I have noticed that this bug is 100% reproducible for me hen I try to start Nautilus right after booting my laptop. If, however, I wait for a few minutes after booting, I can start Nautilus without any delay. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1822351 Title: Nautilus does not open after updating to 19.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1822351/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
