GNOME issueshttps://gitlab.gnome.org/groups/GNOME/-/issues2018-10-28T12:14:34Zhttps://gitlab.gnome.org/GNOME/vala/-/issues/669Show a warning if vapi name doesn't match the package reference of GIR2018-10-28T12:14:34ZRico TzschichholzShow a warning if vapi name doesn't match the package reference of GIRWhen creating a vapi using vapigen check the given library argument against found package reference in GIR source.
[0001-vapigen-Warn-if-the-library-argument-doesn-t-match-a.patch](/uploads/6ceb505f9d87ccb18ba204c48e6fd583/0001-vapigen-W...When creating a vapi using vapigen check the given library argument against found package reference in GIR source.
[0001-vapigen-Warn-if-the-library-argument-doesn-t-match-a.patch](/uploads/6ceb505f9d87ccb18ba204c48e6fd583/0001-vapigen-Warn-if-the-library-argument-doesn-t-match-a.patch)0.44https://gitlab.gnome.org/GNOME/nautilus/-/issues/677crashes when searching2018-10-09T09:17:10ZTobias Kaspercrashes when searching# Steps to reproduce
1. open nautilus
2. search with ctr+f
3. nautilus crashes when by tipping the first key.
Reproducible in:
- Flatpak unstable: crashes less than other but bug still exist.
- other: Ubuntu 18.04.1 LTS, GNOME 3.28...# Steps to reproduce
1. open nautilus
2. search with ctr+f
3. nautilus crashes when by tipping the first key.
Reproducible in:
- Flatpak unstable: crashes less than other but bug still exist.
- other: Ubuntu 18.04.1 LTS, GNOME 3.28.2, nautilus 3.26.4
- Errors with other
```(nautilus:22350): GLib-WARNING **: 14:47:49.479: corrupted double-linked list detected
(nautilus:22350): GLib-WARNING **: 14:47:49.479: corrupted double-linked list detected
[1] 22350 segmentation fault (core dumped) nautilus`
```
- Error messages Flatpak
```** (nautilus:3): WARNING **: 13:03:17.285: Unable to get contents of the bookmarks file: Error opening file /home/tobias/.gtk-bookmarks: No such file or directory
**
ERROR:../src/nautilus-directory.c:862:add_to_hash_table: assertion failed: (g_hash_table_lookup (directory->details->file_hash, name) == NULL)
```
# Current behavior
crashes often by searching
# Expected behavior
no chrash
# Additional information
<!--
Provide more information that could be relevant.
If the issue is a crash, provide a stack trace following the steps in:
https://wiki.gnome.org/Community/GettingInTouch/Bugzilla/GettingTraces
-->
<!-- Ignore the text under this line. -->https://gitlab.gnome.org/GNOME/gnome-builder/-/issues/669rls langserv fails when project has lebicon dependency2018-10-15T20:24:54ZNathaniel McCallumrls langserv fails when project has lebicon dependencySee the repo here: https://github.com/npmccallum/testproj/commits/master
I'm not sure why adding the `lebicon` dependency breaks stuff. Loading `lebicon` directly into Builder works fine. Building the project with the dependency outside...See the repo here: https://github.com/npmccallum/testproj/commits/master
I'm not sure why adding the `lebicon` dependency breaks stuff. Loading `lebicon` directly into Builder works fine. Building the project with the dependency outside Builder works fine. But the LangServ support for RLS silently stops working whenever that dependency appears.https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/669Enabling night mode has no effect2018-10-15T22:50:17ZLionel LandwerlinEnabling night mode has no effectGoing to control center -> display -> night light -> ON has no effect, even during the set hours.
The following warnings appear in syslog when turning it on/off :
```
Oct 15 22:57:37 delly gsd-color[3628]: could not find device: propert...Going to control center -> display -> night light -> ON has no effect, even during the set hours.
The following warnings appear in syslog when turning it on/off :
```
Oct 15 22:57:37 delly gsd-color[3628]: could not find device: property match 'XRANDR_name'='eDP-1' does not exist
Oct 15 22:57:37 delly gsd-color[3628]: could not find device: property match 'XRANDR_name'='eDP-1' does not exist
Oct 15 22:57:37 delly gsd-color[3628]: could not find device: property match 'XRANDR_name'='eDP-1' does not exist
Oct 15 22:57:37 delly gsd-color[3628]: could not find device: property match 'XRANDR_name'='eDP-1' does not exist
Oct 15 22:57:38 delly gsd-color[3628]: could not find device: property match 'XRANDR_name'='eDP-1' does not exist
Oct 15 22:57:38 delly gsd-color[3628]: could not find device: property match 'XRANDR_name'='eDP-1' does not exist
Oct 15 22:57:38 delly gsd-color[3628]: could not find device: property match 'XRANDR_name'='eDP-1' does not exist
Oct 15 22:57:38 delly gsd-color[3628]: could not find device: property match 'XRANDR_name'='eDP-1' does not exist
Oct 15 22:57:38 delly gsd-color[3628]: could not find device: property match 'XRANDR_name'='eDP-1' does not exist
Oct 15 22:57:38 delly gsd-color[3628]: could not find device: property match 'XRANDR_name'='eDP-1' does not exist
Oct 15 22:57:38 delly gsd-color[3628]: could not find device: property match 'XRANDR_name'='eDP-1' does not exist
Oct 15 22:57:38 delly gsd-color[3628]: could not find device: property match 'XRANDR_name'='eDP-1' does not exist
Oct 15 22:57:38 delly gsd-color[3628]: could not find device: property match 'XRANDR_name'='eDP-1' does not exist
Oct 15 22:57:38 delly gsd-color[3628]: could not find device: property match 'XRANDR_name'='eDP-1' does not exist
Oct 15 22:57:38 delly gsd-color[3628]: could not find device: property match 'XRANDR_name'='eDP-1' does not exist
Oct 15 22:57:38 delly gsd-color[3628]: could not find device: property match 'XRANDR_name'='eDP-1' does not exist
Oct 15 22:57:38 delly gsd-color[3628]: could not find device: property match 'XRANDR_name'='eDP-1' does not exist
Oct 15 22:57:38 delly gsd-color[3628]: could not find device: property match 'XRANDR_name'='eDP-1' does not exist
Oct 15 22:57:38 delly gsd-color[3628]: could not find device: property match 'XRANDR_name'='eDP-1' does not exist
Oct 15 22:57:38 delly gsd-color[3628]: could not find device: property match 'XRANDR_name'='eDP-1' does not exist
Oct 15 22:57:38 delly gsd-color[3628]: could not find device: property match 'XRANDR_name'='eDP-1' does not exist
Oct 15 22:57:38 delly gsd-color[3628]: could not find device: property match 'XRANDR_name'='eDP-1' does not exist
Oct 15 22:57:38 delly gsd-color[3628]: could not find device: property match 'XRANDR_name'='eDP-1' does not exist
Oct 15 22:57:38 delly gsd-color[3628]: could not find device: property match 'XRANDR_name'='eDP-1' does not exist
Oct 15 22:57:39 delly gsd-color[3628]: could not find device: property match 'XRANDR_name'='eDP-1' does not exist
Oct 15 22:57:39 delly gsd-color[3628]: could not find device: property match 'XRANDR_name'='eDP-1' does not exist
Oct 15 22:57:39 delly gsd-color[3628]: could not find device: property match 'XRANDR_name'='eDP-1' does not exist
Oct 15 22:57:39 delly gsd-color[3628]: could not find device: property match 'XRANDR_name'='eDP-1' does not exist
Oct 15 22:57:39 delly gsd-color[3628]: could not find device: property match 'XRANDR_name'='eDP-1' does not exist
Oct 15 22:57:40 delly gsd-color[3628]: could not find device: property match 'XRANDR_name'='eDP-1' does not exist
```
This is running on a wayland session.https://gitlab.gnome.org/GNOME/epiphany/-/issues/670Consider styling tab bar in incognito mode2019-02-10T22:05:40ZMichael CatanzaroConsider styling tab bar in incognito mode@exalm, we should consider styling the tab bar in incognito mode so that it is blue, matching the header bar. The colors look a little mismatched currently:
![Screenshot_from_2019-02-05_14-34-18](/uploads/8520c18dacca3d71b7b5490d6d35839...@exalm, we should consider styling the tab bar in incognito mode so that it is blue, matching the header bar. The colors look a little mismatched currently:
![Screenshot_from_2019-02-05_14-34-18](/uploads/8520c18dacca3d71b7b5490d6d358390/Screenshot_from_2019-02-05_14-34-18.png)https://gitlab.gnome.org/GNOME/gnome-software/-/issues/669Remove "Google Plus" web app2019-05-13T15:00:11ZDaniel RusekRemove "Google Plus" web appConsider removing the "Google Plus" web app from GNOME Software. Google Plus was shut down and the app is no longer useful, but is still present in the latest GNOME Software 3.32.2.Consider removing the "Google Plus" web app from GNOME Software. Google Plus was shut down and the app is no longer useful, but is still present in the latest GNOME Software 3.32.2.https://gitlab.gnome.org/GNOME/mutter/-/issues/672[regression] mutter on X11 segfaults in meta_get_overlay_window on startup2019-07-11T09:08:36ZDaniel van Vugtdaniel.van.vugt@canonical.com[regression] mutter on X11 segfaults in meta_get_overlay_window on startupmutter on X11 segfaults in `meta_get_overlay_window` immediately on startup:
```
(gdb) bt
#0 0x00007efdf84349dd in meta_get_overlay_window
(display=0x558a0fd1e000 [MetaDisplay])
at ../src/compositor/compositor.c:1339
#1 0x00007...mutter on X11 segfaults in `meta_get_overlay_window` immediately on startup:
```
(gdb) bt
#0 0x00007efdf84349dd in meta_get_overlay_window
(display=0x558a0fd1e000 [MetaDisplay])
at ../src/compositor/compositor.c:1339
#1 0x00007efdf843ae7b in meta_dnd_init_xdnd
(x11_display=0x558a0fd6c2f0 [MetaX11Display])
at ../src/compositor/meta-dnd.c:121
#2 0x00007efdf84a1f38 in meta_x11_display_new
(display=0x558a0fd1e000 [MetaDisplay], error=0x7ffd3c6eee80)
at ../src/x11/meta-x11-display.c:1347
#3 0x00007efdf84565cf in meta_display_init_x11
(display=0x558a0fd1e000 [MetaDisplay], error=0x7ffd3c6eee80)
at ../src/core/display.c:640
#4 0x00007efdf8456a7c in meta_display_open () at ../src/core/display.c:763
#5 0x00007efdf846855e in meta_run () at ../src/core/main.c:664
#6 0x0000558a0e79638d in main (argc=1, argv=0x7ffd3c6eeff8)
at ../src/core/mutter.c:84
(gdb) list
1334 */
1335 Window
1336 meta_get_overlay_window (MetaDisplay *display)
1337 {
1338 MetaCompositor *compositor = get_compositor_for_display (display);
1339 return compositor->output;
1340 }
1341
1342 /**
1343 * meta_disable_unredirect_for_display:
(gdb) print compositor
$1 = (MetaCompositor *) 0x0
(gdb)
```
I'm hoping this is user error, but it has been a few days since I tried using mutter on X11...Marco Trevisanmail@3v1n0.netMarco Trevisanmail@3v1n0.nethttps://gitlab.gnome.org/GNOME/evolution/-/issues/670CardDAV server not found, when using “Advanced options” for collection accoun...2020-02-19T12:41:07ZДилян Палаузовgit-dpa@aegee.orgCardDAV server not found, when using “Advanced options” for collection account setupI set up a new collection account for email address aaa@milter.aegee.org and under Advanced I enter as server mail.aegee.org . The password is abc (and there are two different users with that password: aaa@milter.aegee.org is the one use...I set up a new collection account for email address aaa@milter.aegee.org and under Advanced I enter as server mail.aegee.org . The password is abc (and there are two different users with that password: aaa@milter.aegee.org is the one user and aaa@aegee.org⇔aaa is the second user).
Evolution asks for the password when doing CalDAV/CardDAV discovery. It calls PROPFIND /dav/addressbooks and obtains the current principle, but does does not query the principle for addressbooks-home-sets.
So at the end of the discovery, a CalDAV server is found, but a CardDAV server is not found.https://gitlab.gnome.org/GNOME/geary/-/issues/677Undo/redo buttons are never sensitive in detached composer2021-01-27T12:01:06ZJames Westmanjames@jwestman.netUndo/redo buttons are never sensitive in detached composerIf you detach the composer to a new window, the undo/redo buttons are insensitive and cannot be used. This happens even if they were sensitive before detaching the composer. The keyboard shortcuts still work, though.
This is on the mast...If you detach the composer to a new window, the undo/redo buttons are insensitive and cannot be used. This happens even if they were sensitive before detaching the composer. The keyboard shortcuts still work, though.
This is on the master branch.https://gitlab.gnome.org/GNOME/gnome-calendar/-/issues/690events added with evolution are shown at the wrong time2021-02-16T15:26:15ZJakobevents added with evolution are shown at the wrong timeOS: Fedora 33 Workstation
evolution 3.38.3 (3.38.3-1.fc33)
gnome-calendar: Version 3.38.2
GNOME Shell 3.38.3 using xorg
kernel 5.10.11-200.fc33.x86_64
Nextcloud 17.0.6
## Summary
When adding an event by accepting an invitation...OS: Fedora 33 Workstation
evolution 3.38.3 (3.38.3-1.fc33)
gnome-calendar: Version 3.38.2
GNOME Shell 3.38.3 using xorg
kernel 5.10.11-200.fc33.x86_64
Nextcloud 17.0.6
## Summary
When adding an event by accepting an invitation in evolution, the resulting calendar entry is shown at the wrong time in gnome calendar. The underlying calendar is a nextcloud calendar.
Evolution:
![image](/uploads/4cafc9c7426539bd0c0e6079060c5fdb/image.png)
gnome-calendar:
![image](/uploads/37776f737e1f2ed7294a7cb28a58b453/image.png)
When you open the event details you see this. Note the inconsistent start times
![image](/uploads/e4009501aa504a89107436c9f98c8cf0/image.png)
It's also incorrect in the "today" section of the gnome shell top panel
![image](/uploads/6e357697dddba9aaef32f597af2fa40e/image.png)
## Steps to reproduce:
<details>
<summary>Example invitation:</summary>
```
--_000_VI1PR02MB39509F4645C066EFC31BB506C58D9VI1PR02MB3950eurp_
Content-Type: text/calendar; charset="utf-8"; method=REQUEST
Content-Transfer-Encoding: 8bit
BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:W. Europe Standard Time
BEGIN:STANDARD
DTSTART:16010101T030000
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=10
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T020000
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN=Test Organizer:mailto:test@xxxxxxxxx.xx
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Jakob
r:mailto:jakob@xxxxxxxx.xx
DESCRIPTION;LANGUAGE=de-DE:\n
UID:040000008200E00074C5B7101A82E00800000000509E9A258DFFD601000000000000000
010000000811C23E681A380459D6118CC6246EC3E
SUMMARY;LANGUAGE=de-DE:test meeting
DTSTART;TZID=W. Europe Standard Time:20210210T130000
DTEND;TZID=W. Europe Standard Time:20210210T133000
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20210210T081434Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:0
LOCATION;LANGUAGE=de-DE:
X-MICROSOFT-CDO-APPT-SEQUENCE:0
X-MICROSOFT-CDO-OWNERAPPTID:XXXXXXXX
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:0
X-MICROSOFT-DONOTFORWARDMEETING:FALSE
X-MICROSOFT-DISALLOW-COUNTER:FALSE
X-MICROSOFT-LOCATIONS:[]
BEGIN:VALARM
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT15M
ACTION:DISPLAY
END:VALARM
END:VEVENT
END:VCALENDAR
--_000_VI1PR02MB39509F4645C066EFC31BB506C58D9VI1PR02MB3950eurp_--
```
</details>
1. Accept an event invitation in evolution.
2. the event was added at the correct time according to the nextcloud web interface and the evolution calendar view
3. gnome-calendar shows the event one hour too latehttps://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/685Printer tab: no padding between unlock and search buttons2020-03-29T22:47:35ZJimmy SciontiPrinter tab: no padding between unlock and search buttonsHi!
Go to Settings > Devices > Printers.
The search button and the unlock button are sticked together. There's no padding/margin between:
![Schermata_da_2019-09-20_08-27-39](/uploads/fb24f6ef818b44673195b6c49f252ce2/Schermata_da_2019-...Hi!
Go to Settings > Devices > Printers.
The search button and the unlock button are sticked together. There's no padding/margin between:
![Schermata_da_2019-09-20_08-27-39](/uploads/fb24f6ef818b44673195b6c49f252ce2/Schermata_da_2019-09-20_08-27-39.png)
Tested on Fedora 31, gnome-shell 3.34.0, gnome-control-center 3.34.0.1, default adwaita theme.https://gitlab.gnome.org/GNOME/pitivi/-/issues/670more rendering problems2018-02-23T18:48:42ZBugzillamore rendering problems## Submitted by Jeff F.T. `@jeff`
Assigned to **Jeff F.T. `@jeff`**
**[Link to original bug (#2382)](https://phabricator.freedesktop.org/T2382)**
## Description
Created attachment 144692
debug log
I have another project file ...## Submitted by Jeff F.T. `@jeff`
Assigned to **Jeff F.T. `@jeff`**
**[Link to original bug (#2382)](https://phabricator.freedesktop.org/T2382)**
## Description
Created attachment 144692
debug log
I have another project file (note to self: "médias numériques et pérennité")
that refuses to render properly. On playback in the timeline, it works fine,
but when I render, it exhibits various problems, as if QoS had made a comeback,
but not just that.
I get:
- a truncated file (even if I render up to 2 mins before hitting the cancel
button... I may end up with an output theora file that has a duration of 12
seconds)
- misplaced/desynched clips (appearing too soon, or too late, etc.)
- a temporary hang during the render process near 1m30 (if you wait long
enough, it continues)
- the usual laggy frames
I made a debug log with GST_DEBUG=3,gnl*:5,*ERR*:5,python:5 PITIVI_DEBUG=5
but I don't know if it's enough.
Imported from https://bugzilla.gnome.org/show_bug.cgi?id=597252https://gitlab.gnome.org/GNOME/gtk/-/issues/670re-position the search bar in GtkShortcutsWindow2018-06-25T23:35:47ZBugzillare-position the search bar in GtkShortcutsWindow## Submitted by Mohammed Sadiq `@pksadiq`
**[Link to original bug (#771233)](https://bugzilla.gnome.org/show_bug.cgi?id=771233)**
## Description
Created attachment 335294
Shortcuts window from GNOME builder (image)
In several appli...## Submitted by Mohammed Sadiq `@pksadiq`
**[Link to original bug (#771233)](https://bugzilla.gnome.org/show_bug.cgi?id=771233)**
## Description
Created attachment 335294
Shortcuts window from GNOME builder (image)
In several applications, the GtkShortcutsWindow is large enough to span the full height of the screen. This introduces several problem with the UI when the search is activated.
1. The close button and the search button is hidden above the clickable area and barely clickable (see attached screenshot)
2. Flickering happens to GtkShortcutsWindow in this case, when search is activated and deactivated.
**Attachment 335294**, "Shortcuts window from GNOME builder (image)":
![GtkShortcutsWindow-old](/uploads/0255812cadb3f449065bf437651634e6/GtkShortcutsWindow-old.png)
Version: 3.21.x
### See also
* [Bug 774075](https://bugzilla.gnome.org/show_bug.cgi?id=774075)https://gitlab.gnome.org/GNOME/evince/-/issues/670Error loading image 'resource:///org/gnome/evince/shell/ui/thumbnail-frame.png'2018-07-06T21:07:06ZBugzillaError loading image 'resource:///org/gnome/evince/shell/ui/thumbnail-frame.png'## Submitted by Laurent Bigonville `@bigon`
**[Link to original bug (#764893)](https://bugzilla.gnome.org/show_bug.cgi?id=764893)**
## Description
Hi,
When starting evince 3.20.0, I see the following warning:
```
Gtk-WARNING **: Er...## Submitted by Laurent Bigonville `@bigon`
**[Link to original bug (#764893)](https://bugzilla.gnome.org/show_bug.cgi?id=764893)**
## Description
Hi,
When starting evince 3.20.0, I see the following warning:
```
Gtk-WARNING **: Error loading image 'resource:///org/gnome/evince/shell/ui/thumbnail-frame.png': La ressource dans « /org/gnome/evince/shell/ui/thumbnail-frame.png » n'existe pas
```
And indeed, gressource shows that `thumbnail-frame.png` is installed in `/org/gnome/evince/ui/thumbnail-frame.png` and not `/org/gnome/evince/**shell**/ui/thumbnail-frame.png`
```
$ gresource list /usr/bin/evince
/org/gnome/evince/gtk/help-overlay.ui
/org/gnome/evince/gtk/menus.ui
/org/gnome/evince/ui/evince.css
/org/gnome/evince/ui/thumbnail-frame.png
```
Version: 3.20.xhttps://gitlab.gnome.org/GNOME/gimp/-/issues/670GIMP crashes if it runs out of memory, e.g. if you try to open too many image...2023-08-08T02:24:53ZBugzillaGIMP crashes if it runs out of memory, e.g. if you try to open too many images at once## Submitted by Gary
**[Link to original bug (#748469)](https://bugzilla.gnome.org/show_bug.cgi?id=748469)**
## Description
Created attachment 302351
Screenshot of first error message
To Reproduce:
I dragged and dropped 24 jpg imag...## Submitted by Gary
**[Link to original bug (#748469)](https://bugzilla.gnome.org/show_bug.cgi?id=748469)**
## Description
Created attachment 302351
Screenshot of first error message
To Reproduce:
I dragged and dropped 24 jpg images (about 58MB) total into the GIMP.
Actual Result:
After loading most of the images (I don't know how many), The GIMP shows the message in the attachment.
After the message in the attachment, the following appears:
---------------------------
Microsoft Visual C++ Runtime Library
---------------------------
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
then Windows kills The GIMP.
The second time I tried this, GIMP just crashed.
Expected Result:
The images load properly so that I can work with them.
I suspect I am trying to load too much into The GIMP. I'd prefer that The GIMP tell me nicely to not load so much at once instead of crashing.
Win 7/32, 4GB RAM, GIMP 2.8.14
**Attachment 302351**, "Screenshot of first error message":
![screenshot](/uploads/d20114c4f0860d1008e6f568f5f8003d/screenshot.png)
Version: 2.8.14https://gitlab.gnome.org/GNOME/vala/-/issues/670Support g_autoptr() and emit G_DEFINE_AUTOPTR_CLEANUP_FUNC calls2019-10-01T06:52:49ZRico TzschichholzSupport g_autoptr() and emit G_DEFINE_AUTOPTR_CLEANUP_FUNC callsIf an library is developed it is required to define the appropriate cleanup functions to allow g_autoptr() being used.
This is supported by glib >= 2.44.
[0001-codegen-Emit-G_DEFINE_AUTOPTR_CLEANUP_FUNC-for-class.patch](/uploads/366c7...If an library is developed it is required to define the appropriate cleanup functions to allow g_autoptr() being used.
This is supported by glib >= 2.44.
[0001-codegen-Emit-G_DEFINE_AUTOPTR_CLEANUP_FUNC-for-class.patch](/uploads/366c7ca7908754eed183e9843e7e17ba/0001-codegen-Emit-G_DEFINE_AUTOPTR_CLEANUP_FUNC-for-class.patch)0.44https://gitlab.gnome.org/GNOME/nautilus/-/issues/678Crash when I open file from nautilus (floating)2018-10-15T14:02:43ZDDRCrash when I open file from nautilus (floating)```
Oct 6 20:57:35 debian gnome-shell[1213]: value "-1.000000" of type 'gfloat' is invalid or out of range for property 'width' of type 'gfloat'
Oct 6 20:57:35 debian gnome-shell[1213]: value "-1.000000" of type 'gfloat' is invalid or ...```
Oct 6 20:57:35 debian gnome-shell[1213]: value "-1.000000" of type 'gfloat' is invalid or out of range for property 'width' of type 'gfloat'
Oct 6 20:57:35 debian gnome-shell[1213]: value "-1.000000" of type 'gfloat' is invalid or out of range for property 'height' of type 'gfloat'
Oct 6 20:57:35 debian gnome-shell[1213]: value "-1.000000" of type 'gfloat' is invalid or out of range for property 'width' of type 'gfloat'
Oct 6 20:57:35 debian gnome-shell[1213]: value "-1.000000" of type 'gfloat' is invalid or out of range for property 'height' of type 'gfloat'
Oct 6 20:58:18 debian kernel: [35526.135761] nautilus[5482]: segfault at 80000001a ip 00007f22164bb59c sp 00007ffd2c955dc8 error 4 in libgobject-2.0.so.0.5800.0[7f2216492000+31000]
Oct 6 20:58:18 debian kernel: [35526.135770] Code: fa fc 03 00 00 77 37 48 c1 ea 02 48 8d 05 5c ed 01 00 48 8b 14 d0 48 81 fe fc 03 00 00 76 2c 48 83 e6 fc 31 c0 48 85 d2 74 37 <f6> 42 16 04 74 05 48 85 f6 75 31 31 c0 c3 66 0f 1f 44 00 00 48 83
Oct 6 20:58:19 debian gnome-shell[1213]: STACK_OP_RAISE_ABOVE: sibling window 0x2409587 not in stack
Oct 6 20:58:19 debian gnome-shell[1213]: STACK_OP_RAISE_ABOVE: sibling window 0x2409587 not in stack
Oct 6 20:58:20 debian gnome-shell[1213]: STACK_OP_RAISE_ABOVE: sibling window 0x2409587 not in stack
```
Debian x64
Gnome 3.30.0https://gitlab.gnome.org/GNOME/gnome-builder/-/issues/670Devhelp text does not fit in popup2018-10-15T21:11:25ZAndrej GricenkoDevhelp text does not fit in popupDocumentation popup crops function signature at right side when it is too long
![Снимок_экрана_от_2018-10-15_23-42-46](/uploads/0d3155ade09b263ad4f388884fed58f0/Снимок_экрана_от_2018-10-15_23-42-46.png).Documentation popup crops function signature at right side when it is too long
![Снимок_экрана_от_2018-10-15_23-42-46](/uploads/0d3155ade09b263ad4f388884fed58f0/Снимок_экрана_от_2018-10-15_23-42-46.png).https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/670XDG_CURRENT_DESKTOP=unity crashes gnome-shell 3.28.32018-10-16T17:01:17ZGhost UserXDG_CURRENT_DESKTOP=unity crashes gnome-shell 3.28.3After upgrading from 3.28.1 to 3.28.3 on Fedora 28 I was unable to log into my account since gnome-shell would crash on startup:
```
Okt 15 17:54:36 localhost.localdomain gnome-shell[1195]: JS ERROR: TypeError: this._currentWindow is nu...After upgrading from 3.28.1 to 3.28.3 on Fedora 28 I was unable to log into my account since gnome-shell would crash on startup:
```
Okt 15 17:54:36 localhost.localdomain gnome-shell[1195]: JS ERROR: TypeError: this._currentWindow is null
_setCurrentRect@resource:///org/gnome/shell/ui/keyboard.js:536:13
wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22
_init/<@resource:///org/gnome/shell/ui/keyboard.js:503:13
Okt 15 17:54:36 localhost.localdomain gnome-shell[1195]: JS ERROR: TypeError: this._currentWindow is null
_setCurrentRect@resource:///org/gnome/shell/ui/keyboard.js:536:13
wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22
_init/<@resource:///org/gnome/shell/ui/keyboard.js:503:13
Okt 15 17:54:36 localhost.localdomain gnome-shell[1195]: Object Clutter.Clone (0x55c0071607f0), has been already finalized. Impossible to get any property from it.
Okt 15 17:54:36 localhost.localdomain org.gnome.Shell.desktop[1195]: == Stack trace for context 0x55c005b8c230 ==
Okt 15 17:54:36 localhost.localdomain org.gnome.Shell.desktop[1195]: #0 0x7ffccfcf1200 b resource:///org/gnome/shell/ui/tweener.js:73 (0x7fe3580c8cd0 @ 9)
Okt 15 17:54:36 localhost.localdomain org.gnome.Shell.desktop[1195]: #1 0x7ffccfcf19c0 b resource:///org/gnome/shell/ui/tweener.js:105 (0x7fe3580c8f78 @ 36)
Okt 15 17:54:36 localhost.localdomain org.gnome.Shell.desktop[1195]: #2 0x7ffccfcf1a60 b resource:///org/gnome/shell/ui/tweener.js:92 (0x7fe3580c8de0 @ 52)
Okt 15 17:54:36 localhost.localdomain org.gnome.Shell.desktop[1195]: #3 0x7ffccfcf2640 I resource:///org/gnome/gjs/modules/tweener/tweener.js:208 (0x7fe3580d2918 @ 54)
Okt 15 17:54:36 localhost.localdomain org.gnome.Shell.desktop[1195]: #4 0x7ffccfcf2790 b resource:///org/gnome/gjs/modules/tweener/tweener.js:337 (0x7fe3580d29a0 @ 1626)
Okt 15 17:54:36 localhost.localdomain org.gnome.Shell.desktop[1195]: #5 0x7ffccfcf2840 b resource:///org/gnome/gjs/modules/tweener/tweener.js:350 (0x7fe3580d2a28 @ 100)
Okt 15 17:54:36 localhost.localdomain org.gnome.Shell.desktop[1195]: #6 0x7ffccfcf28d0 b resource:///org/gnome/gjs/modules/tweener/tweener.js:365 (0x7fe3580d2ab0 @ 10)
Okt 15 17:54:36 localhost.localdomain org.gnome.Shell.desktop[1195]: #7 0x7ffccfcf2950 I resource:///org/gnome/gjs/modules/signals.js:128 (0x7fe3580cff78 @ 386)
Okt 15 17:54:36 localhost.localdomain org.gnome.Shell.desktop[1195]: #8 0x7ffccfcf2a00 b resource:///org/gnome/shell/ui/tweener.js:207 (0x7fe3580cf5e8 @ 159)
Okt 15 17:54:36 localhost.localdomain org.gnome.Shell.desktop[1195]: #9 0x7ffccfcf2a70 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fe3580b5de0 @ 71)
Okt 15 17:54:36 localhost.localdomain org.gnome.Shell.desktop[1195]: #10 0x7ffccfcf2a70 I resource:///org/gnome/shell/ui/tweener.js:182 (0x7fe3580cf560 @ 15)
Okt 15 17:54:36 localhost.localdomain org.gnome.Shell.desktop[1195]: == Stack trace for context 0x55c005b8c230 ==
Okt 15 17:54:36 localhost.localdomain org.gnome.Shell.desktop[1195]: #0 0x7ffccfcf1200 b resource:///org/gnome/shell/ui/tweener.js:80 (0x7fe3580c8cd0 @ 82)
Okt 15 17:54:36 localhost.localdomain org.gnome.Shell.desktop[1195]: #1 0x7ffccfcf19c0 b resource:///org/gnome/shell/ui/tweener.js:105 (0x7fe3580c8f78 @ 36)
Okt 15 17:54:36 localhost.localdomain org.gnome.Shell.desktop[1195]: #2 0x7ffccfcf1a60 b resource:///org/gnome/shell/ui/tweener.js:92 (0x7fe3580c8de0 @ 52)
Okt 15 17:54:36 localhost.localdomain org.gnome.Shell.desktop[1195]: #3 0x7ffccfcf2640 I resource:///org/gnome/gjs/modules/tweener/tweener.js:208 (0x7fe3580d2918 @ 54)
Okt 15 17:54:36 localhost.localdomain org.gnome.Shell.desktop[1195]: #4 0x7ffccfcf2790 b resource:///org/gnome/gjs/modules/tweener/tweener.js:337 (0x7fe3580d29a0 @ 1626)
Okt 15 17:54:36 localhost.localdomain org.gnome.Shell.desktop[1195]: #5 0x7ffccfcf2840 b resource:///org/gnome/gjs/modules/tweener/tweener.js:350 (0x7fe3580d2a28 @ 100)
Okt 15 17:54:36 localhost.localdomain org.gnome.Shell.desktop[1195]: #6 0x7ffccfcf28d0 b resource:///org/gnome/gjs/modules/tweener/tweener.js:365 (0x7fe3580d2ab0 @ 10)
Okt 15 17:54:36 localhost.localdomain org.gnome.Shell.desktop[1195]: #7 0x7ffccfcf2950 I resource:///org/gnome/gjs/modules/signals.js:128 (0x7fe3580cff78 @ 386)
Okt 15 17:54:36 localhost.localdomain org.gnome.Shell.desktop[1195]: #8 0x7ffccfcf2a00 b resource:///org/gnome/shell/ui/tweener.js:207 (0x7fe3580cf5e8 @ 159)
Okt 15 17:54:36 localhost.localdomain gnome-shell[1195]: Object Clutter.Clone (0x55c0071607f0), has been already finalized. Impossible to set any property to it.
Okt 15 17:54:36 localhost.localdomain org.gnome.Shell.desktop[1195]: #9 0x7ffccfcf2a70 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fe3580b5de0 @ 71)
Okt 15 17:54:36 localhost.localdomain org.gnome.Shell.desktop[1195]: #10 0x7ffccfcf2a70 I resource:///org/gnome/shell/ui/tweener.js:182 (0x7fe3580cf560 @ 15)
Okt 15 17:54:39 localhost.localdomain gnome-shell[1195]: JS ERROR: TypeError: this._currentWindow is null
_setCurrentRect@resource:///org/gnome/shell/ui/keyboard.js:536:13
wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22
_init/<@resource:///org/gnome/shell/ui/keyboard.js:503:13
popModal@resource:///org/gnome/shell/ui/main.js:497:9
_releaseModalGrab@resource:///org/gnome/shell/ui/grabHelper.js:222:9
wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22
ungrab@resource:///org/gnome/shell/ui/grabHelper.js:269:13
wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22
_onMenuOpenState@resource:///org/gnome/shell/ui/popupMenu.js:1294:13
wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22
_emit@resource:///org/gnome/gjs/modules/signals.js:128:27
close@resource:///org/gnome/shell/ui/popupMenu.js:888:9
wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22
itemActivated@resource:///org/gnome/shell/ui/popupMenu.js:527:9
wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22
_connectItemSignals/menuItem._activateId<@resource:///org/gnome/shell/ui/popupMenu.js:563:13
_emit@resource:///org/gnome/gjs/modules/signals.js:128:27
activate@resource:///org/gnome/shell/ui/popupMenu.js:166:9
wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22
_onButtonReleaseEvent@resource:///org/gnome/shell/ui/popupMenu.js:127:9
wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22
```
Which looks like it could be related to #414.
It turned out removing
```
XDG_CURRENT_DESKTOP=unity
```
from my `.bashrc` also removed the crash.
(Which is in my `.bashrc` to make third party software usable again after the removal of the notification area)https://gitlab.gnome.org/GNOME/epiphany/-/issues/671The website link in the about menu should open in Epiphany2019-02-07T21:48:02ZRoland TaylorThe website link in the about menu should open in EpiphanyWhen you click the website link in Epiphany's about menu, it opens in whatever browser is set as default, like say, Firefox. This shouldn't be the case as Epiphany is a browser itself.When you click the website link in Epiphany's about menu, it opens in whatever browser is set as default, like say, Firefox. This shouldn't be the case as Epiphany is a browser itself.