[Bug 2065467] Re: GIMP crashed when exporting PNG

2024-05-10 Thread Zalán Hári 
*** This bug is a duplicate of bug 2055044 ***
https://bugs.launchpad.net/bugs/2055044

** This bug has been marked a duplicate of bug 2055044
   GIMP crash at closure on systems with GLib 2.80.0 (and 2.79.x)

-- 
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/2065467

Title:
  GIMP crashed when exporting PNG

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/2065467/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2055012] Re: When I upgraded from 22.04 to 24.04, DNS resolution went wrong.

2024-04-16 Thread Zalán Hári 
** Description changed:

  I was an unpatient idiot, and I upgraded from 22.04 to 24.04. Near to
  the end of the upgrade, I got an „Oh, no! Something has gone wrong and
  the system cannot recover. Call the system administrator” message after
  a red FAILED in the terminal. The system administrator is myself,
  because my computer is a personal one. Hard reset, same error,
  Ctrl+Alt+F3, sudo apt reinstall gdm3. Obviously. I needed to finish the
  update with dpkg. While dpkg was upgrading, it printed an error message
  for every WiFi connection:
  
  „[Failed] Failed to migrate [I do not remember, something with
  /etc/netplan]”
  
- It took at least one and a half our to find the solution on Ask Ubuntu.
+ It took at least one and a half hour to find the solution on Ask Ubuntu.
  The problem was: /etc/resolv.conf became a broken link, along with
  systemd-resolve.service. I needed to remove both of them and write a new
  resolv.conf to fix the error.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: network-manager 1.45.90-1ubuntu1
  ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
  Uname: Linux 6.6.0-14-generic x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 26 08:21:02 2024
  InstallationDate: Installed on 2023-07-05 (236 days ago)
  InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316)
  IpRoute:
   default via 192.168.0.1 dev wlp3s0 proto dhcp src 192.168.0.100 metric 600
   192.168.0.0/24 dev wlp3s0 proto kernel scope link src 192.168.0.100 metric 
600
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to noble on 2024-02-24 (2 days ago)
  modified.conffile..etc.init.d.apport: [modified]
  mtime.conffile..etc.init.d.apport: 2024-02-22T15:20:00
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.45.90  connected  started  full  enabled enabled  
enabled  missing  enabled

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/2055012

Title:
  When I upgraded from 22.04 to 24.04, DNS resolution went wrong.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2055012/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2060613] [NEW] Gedit sometimes crashes by segmentation fault at closure

2024-04-08 Thread Zalán Hári 
Public bug reported:

When I do not wait until the document is fully saved (or I only wait a
short interval) gedit crashes with segmentation fault after a few
seconds. It has not lead to data loss yet, but it is truly unpleasant,
let alone if we include that otherwise it floods the terminal with
critical GTK errors... (bug #2055010)

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: gedit 46.2-1build1
ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
Uname: Linux 6.8.0-22-generic x86_64
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr  9 07:16:42 2024
InstallationDate: Installed on 2023-07-05 (279 days ago)
InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316)
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
SourcePackage: gedit
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.init.d.apport: [modified]
mtime.conffile..etc.init.d.apport: 2024-02-22T15:20:00

** Affects: gedit (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug noble wayland-session

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/2060613

Title:
  Gedit sometimes crashes by segmentation fault at closure

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/2060613/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2060611] [NEW] I get login keyring unlock problem every startup

2024-04-08 Thread Zalán Hári 
Public bug reported:

I am using Noble Numbat alpha. I was hoping that I get the beta version
and everything will be more stable. But the beta has been delayed, and
after an upgrade at April 5 2024, something has gone wrong. Now, every
time I log in after startup, I get the following message:

„The login keyring did not get unlocked when you logged into your
computer”.


Fixing that bug would probably improve the user experience a bit.

GDM version: 46.0


PS: It is possible that it is a problem with gnome-session rather than GDM.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: gdm3 46.0-2ubuntu1
ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
Uname: Linux 6.8.0-22-generic x86_64
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr  9 07:07:53 2024
InstallationDate: Installed on 2023-07-05 (279 days ago)
InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316)
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
SourcePackage: gdm3
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.init.d.apport: [modified]
modified.conffile..etc.pam.d.gdm-password: [modified]
mtime.conffile..etc.gdm3.custom.conf: 2023-08-04T18:46:39.585253
mtime.conffile..etc.init.d.apport: 2024-02-22T15:20:00
mtime.conffile..etc.pam.d.gdm-password: 2023-08-04T18:47:38.965793

** Affects: gdm3 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug noble wayland-session

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/2060611

Title:
  I get login keyring unlock problem every startup

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2060611/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2058000] Re: When I click „Quit” in the Dock, gdm3 crashes and prints quirky binary output

2024-03-14 Thread Zalán Hári 
Now, I was able to close Opera without any problem. Interesting.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/2058000

Title:
  When I click „Quit” in the Dock, gdm3 crashes and prints quirky binary
  output

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2058000/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2058000] [NEW] When I click „Quit” in the Dock, gdm3 crashes and prints quirky binary output

2024-03-14 Thread Zalán Hári 
Public bug reported:

When I try to close any application with „Quit” in the Dock, GDM
crashes, prints something such as that:

@^@^@^@^@

Then it throws me to the login screen.

GDM3 version: 45.0.1-1ubuntu2
Ubuntu release: 24.04 Noble Numbat

I do not have more information.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: gdm3 45.0.1-1ubuntu2
ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
Uname: Linux 6.8.0-11-generic x86_64
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 15 07:22:53 2024
InstallationDate: Installed on 2023-07-05 (254 days ago)
InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316)
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
SourcePackage: gdm3
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.init.d.apport: [modified]
mtime.conffile..etc.gdm3.custom.conf: 2023-08-04T18:46:39.585253
mtime.conffile..etc.init.d.apport: 2024-02-22T15:20:00
mtime.conffile..etc.pam.d.gdm-password: 2023-08-04T18:47:38.965793

** Affects: gdm3 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug noble wayland-session

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/2058000

Title:
  When I click „Quit” in the Dock, gdm3 crashes and prints quirky binary
  output

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2058000/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2057997] [NEW] GIMP crashes by segmentation fault when I try to close it without saving

2024-03-14 Thread Zalán Hári 
Public bug reported:

GIMP crashes by segmentation fault every time when I close it without
saving, the complete message is the following (version: 2.10.36-2, OS:
24.04 Noble Numbat):




```
GNU Image Manipulation Program version 2.10.36
git-describe: GIMP_2_10_36
Build: unknown rev 0 for linux
# C compiler #
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-linux-gnu/13/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none:amdgcn-amdhsa
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu 
13.2.0-7ubuntu1' --with-bugurl=file:///usr/share/doc/gcc-13/README.Bugs 
--enable-languages=c,ada,c++,go,d,fortran,objc,obj-c++,m2 --prefix=/usr 
--with-gcc-major-version-only --program-suffix=-13 
--program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id 
--libexecdir=/usr/libexec --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-plugin --enable-default-pie --with-system-zlib 
--enable-libphobos-checking=release --with-target-system-zlib=auto 
--enable-objc-gc=auto --enable-multiarch --disable-werror --enable-cet 
--with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 
--enable-multilib --with-tune=generic 
--enable-offload-targets=nvptx-none=/build/gcc-13-p2aSDx/gcc-13-13.2.0/debian/tmp-nvptx/usr,amdgcn-amdhsa=/build/gcc-13-p2aSDx/gcc-13-13.2.0/debian/tmp-gcn/usr
 --enable-offload-defaulted --without-cuda-driver --enable-checking=release 
--build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu 
--with-build-config=bootstrap-lto-lean --enable-link-serialization=2
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 13.2.0 (Ubuntu 13.2.0-7ubuntu1) 

# Libraries #
using babl version 0.1.108 (compiled against version 0.1.106)
using GEGL version 0.4.48 (compiled against version 0.4.44)
using GLib version 2.79.2 (compiled against version 2.78.1)
using GdkPixbuf version 2.42.10 (compiled against version 2.42.10)
using GTK+ version 2.24.33 (compiled against version 2.24.33)
using Pango version 1.51.0 (compiled against version 1.51.0)
using Fontconfig version 2.15.0 (compiled against version 2.14.2)
using Cairo version 1.18.0 (compiled against version 1.18.0)

```
> fatal error: Segmentation fault

Stack trace:
```

# Stack traces obtained from PID 428330 - Thread 428330 #


This GDB supports auto-downloading debuginfo from the following URLs:
  
Enable debuginfod for this session? (y or [n]) [answered N; input not from 
terminal]
Debuginfod has been disabled.
To make this setting permanent, add 'set debuginfod enabled off' to .gdbinit.
[New LWP 428469]
[New LWP 428437]
[New LWP 428408]
[New LWP 428399]
[New LWP 428398]
[New LWP 428397]
[New LWP 428389]
[New LWP 428388]
[New LWP 428387]
[New LWP 428386]
[New LWP 428385]
[New LWP 428384]
[New LWP 428383]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x7eea3cd1ba8a in __GI___libc_read (nbytes=256, buf=0x7ffc99daeed0, fd=27) 
at ../sysdeps/unix/sysv/linux/read.c:26
  Id   Target Id Frame 
* 1Thread 0x7eea3c6fd3c0 (LWP 428330) "gimp-2.10"0x7eea3cd1ba8a in 
__GI___libc_read (nbytes=256, buf=0x7ffc99daeed0, fd=27) at 
../sysdeps/unix/sysv/linux/read.c:26
  2Thread 0x7eea1cc006c0 (LWP 428469) "swap writer"  syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  3Thread 0x7eea07e006c0 (LWP 428437) "threaded-ml"  0x7eea3cd1b4bd in 
__GI___poll (fds=0x7ee9b004b8e0, nfds=2, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
  4Thread 0x7eea074006c0 (LWP 428408) "async"syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  5Thread 0x7eea1fe006c0 (LWP 428399) "gdbus"0x7eea3cd1b4bd in 
__GI___poll (fds=0x7ee9fc000b90, nfds=3, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
  6Thread 0x7eea1f4006c0 (LWP 428398) "gmain"0x7eea3cd1b4bd in 
__GI___poll (fds=0x5df1623bca00, nfds=2, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
  7Thread 0x7eea1ea006c0 (LWP 428397) "pool-spawner" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  8Thread 0x7eea33e006c0 (LWP 428389) "worker"   syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  9Thread 0x7eea38c006c0 (LWP 428388) "worker"   syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  10   Thread 0x7eea396006c0 (LWP 428387) "worker"   syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  11   Thread 0x7eea3a0006c0 (LWP 428386) "worker"   syscall () at 
../sysdeps/unix/sysv/linux/x86_64/

[Bug 2055012] Re: When I upgraded from 22.04 to 24.04, DNS resolution went wrong.

2024-03-08 Thread Zalán Hári 
I did not try that and I hope that I will not need to, but sudo apt
install systemd-resolved seems to be much better.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/2055012

Title:
  When I upgraded from 22.04 to 24.04, DNS resolution went wrong.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2055012/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2055010] Re: Gedit has an invalid regular expression, the error is not fatal, but immediately occurs at its start, additionally, it has a critical level GTK error as well

2024-03-01 Thread Zalán Hári 
** Changed in: gedit (Ubuntu)
 Assignee: (unassigned) => Zalán Hári (zalanhari)

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/2055010

Title:
  Gedit has an invalid regular expression, the error is not fatal, but
  immediately occurs at its start, additionally, it has a critical level
  GTK error as well

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/2055010/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1970743] Re: Gedit not changing themes when run as root in Ubuntu 22.04

2024-02-28 Thread Zalán Hári 
On Ubuntu 24.04 Noble Numbat, it is working.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/1970743

Title:
  Gedit not changing themes when run as root in Ubuntu 22.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1970743/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2055010] Re: Gedit has an invalid regular expression, the error is not fatal, but immediately occurs at its start, additionally, it has a critical level GTK error as well

2024-02-28 Thread Zalán Hári 
I clarify: the critical message occurs exactly 248 times at every close
if I count it with „gedit 2> /dev/stdout | wc -l”.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/2055010

Title:
  Gedit has an invalid regular expression, the error is not fatal, but
  immediately occurs at its start, additionally, it has a critical level
  GTK error as well

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/2055010/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2055010] Re: Gedit has an invalid regular expression, the error is not fatal, but immediately occurs at its start, additionally, it has a critical level GTK error as well

2024-02-26 Thread Zalán Hári 
Sorry, there is a mistake in my bug report: the critical GTK error
occurs when I close gedit.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/2055010

Title:
  Gedit has an invalid regular expression, the error is not fatal, but
  immediately occurs at its start, additionally, it has a critical level
  GTK error as well

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/2055010/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2055010] [NEW] Gedit has an invalid regular expression, the error is not fatal, but immediately occurs at its start, additionally, it has a critical level GTK error as well

2024-02-25 Thread Zalán Hári 
Public bug reported:

When the unstable sudo apt-get autoremove removed Gedit, I reinstalled 
it (with the removed necessary Python packages). When I started it first time 
from the terminal, I got the following message:
/usr/lib/x86_64-linux-gnu/gedit/plugins/externaltools/library.py:212: 
SyntaxWarning: invalid escape sequence '\-'
  RE_KEY = re.compile('^([a-zA-Z_][a-zA-Z0-9_.\-]*)(\[([a-zA-Z_@]+)\])?$')

I was able to fix that with replacing \- to \\-, \[ to \\[ and \] to
\\], but an average user will have extreme computer rage from it and
s/he will shoot the computer. And, in addition, this problem probably
makes gedit less efficient.

The huger problem is:
„(gnome-text-editor:31580): Gtk-CRITICAL **: 07:40:03.163: 
gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed”
Imagine it circa 1000 times.

I attached a quick-and-dirty patch to the first problem.

The additional necessary information has been included by apport.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: gedit 46.1-3 [modified: 
usr/lib/x86_64-linux-gnu/gedit/plugins/externaltools/library.py]
ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
Uname: Linux 6.6.0-14-generic x86_64
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Feb 26 08:04:39 2024
InstallationDate: Installed on 2023-07-05 (236 days ago)
InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316)
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
SourcePackage: gedit
UpgradeStatus: Upgraded to noble on 2024-02-24 (2 days ago)
modified.conffile..etc.init.d.apport: [modified]
mtime.conffile..etc.init.d.apport: 2024-02-22T15:20:00

** Affects: gedit (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug noble

** Patch added: "library.py"
   https://bugs.launchpad.net/bugs/2055010/+attachment/5749380/+files/library.py

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/2055010

Title:
  Gedit has an invalid regular expression, the error is not fatal, but
  immediately occurs at its start, additionally, it has a critical level
  GTK error as well

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/2055010/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs