[Bug 2049269] Re: In recent updates, things started to freeze a lot when working with text (probably when working with layers, I work mostly in text), the text box works incorrectly
I'm sorry, after the crash I haven't seen any more of these freezes, only the caret bug remains (and of course the crash itself) -- 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/2049269 Title: In recent updates, things started to freeze a lot when working with text (probably when working with layers, I work mostly in text), the text box works incorrectly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/2049269/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2049269] [NEW] In recent updates, things started to freeze a lot when working with text (probably when working with layers, I work mostly in text), the text box works incorrectly
Public bug reported: These bugs are probably related, so I will list them here. After a recent update, there is a bug where when working with text, when the caret is placed in any position, the position starts to change a few characters earlier. Also when inserting text, sometimes there is a freeze. At one point, when trying to resize a text layer, GIMP ended with an error ``` GNU Image Manipulation Program version 2.10.30 git-describe: GIMP_2_10_30 Build: unknown rev 0 for linux # C compiler # Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/11/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 11.4.0-1ubuntu1~22.04' --with-bugurl=file:///usr/share/doc/gcc-11/README.Bugs --enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++,m2 --prefix=/usr --with-gcc-major-version-only --program-suffix=-11 --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-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-11-XeT9lY/gcc-11-11.4.0/debian/tmp-nvptx/usr,amdgcn-amdhsa=/build/gcc-11-XeT9lY/gcc-11-11.4.0/debian/tmp-gcn/usr --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 11.4.0 (Ubuntu 11.4.0-1ubuntu1~22.04) # Libraries # using babl version 0.1.92 (compiled against version 0.1.92) using GEGL version 0.4.34 (compiled against version 0.4.34) using GLib version 2.72.4 (compiled against version 2.72.4) using GdkPixbuf version 2.42.8 (compiled against version 2.42.8) using GTK+ version 2.24.33 (compiled against version 2.24.33) using Pango version 1.50.6 (compiled against version 1.50.6) 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: Ошибка сегментирования Stack trace: ``` # Stack traces obtained from PID 312250 - Thread 312250 # [New LWP 312251] [New LWP 312252] [New LWP 312253] [New LWP 312254] [New LWP 312255] [New LWP 312256] [New LWP 312257] [New LWP 312258] [New LWP 312259] [New LWP 312261] [New LWP 312303] [New LWP 312306] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". __GI___libc_read (nbytes=256, buf=0x7ffe1feb3290, fd=19) at ../sysdeps/unix/sysv/linux/read.c:26 Id Target IdFrame * 1Thread 0x7fbbffd4ee80 (LWP 312250) "gimp-2.10" __GI___libc_read (nbytes=256, buf=0x7ffe1feb3290, fd=19) at ../sysdeps/unix/sysv/linux/read.c:26 2Thread 0x7fbbff385640 (LWP 312251) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 3Thread 0x7fbbfeb84640 (LWP 312252) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 4Thread 0x7fbbfe383640 (LWP 312253) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 5Thread 0x7fbbf7fff640 (LWP 312254) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 6Thread 0x7fbbfdb82640 (LWP 312255) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 7Thread 0x7fbbfd381640 (LWP 312256) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 8Thread 0x7fbbfcb80640 (LWP 312257) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 9Thread 0x7fbbf7638640 (LWP 312258) "gmain" 0x7fbc00918bcf in __GI___poll (fds=0x55f82d01e660, nfds=2, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 10 Thread 0x7fbbf6e37640 (LWP 312259) "gdbus" 0x7fbc00918bcf in __GI___poll (fds=0x55f82d037120, nfds=3, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 11 Thread 0x7fbbcb9ff640 (LWP 312261) "async" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 12 Thread 0x7fbbcb1fe640 (LWP 312303) "swap writer" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 13 Thread 0x7fbbca9fd640 (LWP 312306) "paint" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
[Bug 1950393] Re: GDM session crashes on suspend on Ubuntu 21.10
Hi Daniel, In my understanding, the crash is not reproducible after my workaround (switching to the nvidia driver), because the nvidia-resume.service is not masked (my theory). Therefore, I switched back to the Nouveau driver, and I reproduced the problem and collected the system logs as you asked. Now prevboot.txt contains the logs from a clean boot, through the session crash and ends with a (user requested) reboot. Just for the record, these are the steps to reproduce the bug: 1. Install Ubuntu 21.10 on a laptop(?) with an nvidia GPU 2. Open "Software & Updates" -> "Additional Drivers" 3. Select the latest driver (470) 4. Reboot 5. Login normally on GDM 6. Open "Software & Updates" -> "Additional Drivers" 7. Select "Nouveau display driver" and apply the changes 8. Reboot 9. Login normally on GDM 10. Try to suspend the system 11. You should observe a session crash here ** Attachment added: "System journal for the previous boot, as requested in update #8" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1950393/+attachment/5540130/+files/prevboot.txt -- 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/1950393 Title: GDM session crashes on suspend on Ubuntu 21.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1950393/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1950393] Re: GDM session crashes on suspend on Ubuntu 21.10
Interesting update Given the "Unit nvidia-resume.service is masked" complain by systemd- logind in my previous comment, I thought it could be related with the switching on and off the proprietary nvidia driver: after turning it on, I turned it off (switching to Nouveau) because of this other bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947614 So, I opened the "Software & Updates" tool and in "Additional Drivers" I turned nvidia-driver-470 on again and... voila', the session-crash-on-suspend bug disappeared. It looks like to me that the tool messed up some systemd units like nvidia-resume.service and it didn't return them to the previous state after I switched back to Nouveau. Note: the only thing I used to turn on and off the nvidia driver is that "Software & Updates" tool, no custom configurations/hacks at all. -- 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/1950393 Title: GDM session crashes on suspend on Ubuntu 21.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1950393/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1950393] Re: GDM session crashes on suspend on Ubuntu 21.10
If I grep for `systemd`, after the first meaningful message: Nov 10 00:20:06 lenovo systemd-logind[11553]: Power key pressed. The first error is: Nov 10 00:20:11 lenovo systemd-logind[11553]: Error during inhibitor- delayed operation (already returned success to client): Unit nvidia- resume.service is masked. And later: Nov 10 00:20:13 lenovo /usr/libexec/gdm-x-session[12386]: (EE) systemd- logind disappeared (stopped/restarted?) ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New -- 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/1950393 Title: GDM session crashes on suspend on Ubuntu 21.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1950393/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1950393] Re: GDM session crashes on suspend on Ubuntu 21.10
Hi Daniel, unfortunately, there are no crash files in /var/crash/. I've checked also: https://errors.ubuntu.com/user/ but there are no crashes reported in the last month. It looks like the "crash" is not caused by a fatal signal like SIGSEGV and no core dump is generated. But, still from the same log file (attached), I noticed that systemd- logind exited with a failure: -- Nov 10 00:20:13 lenovo upowerd[3602]: Could not acquire inhibitor lock: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying Nov 10 00:20:13 lenovo dbus-daemon[1120]: [system] Activating via systemd: service name='org.freedesktop.login1' unit='dbus-org.freedesktop.login1.service' requested by ':1.178' (uid=1000 pid=12386 comm="/usr/lib/xorg/Xorg vt2 -displayfd 3 -auth /run/use" label="unconfined") Nov 10 00:20:13 lenovo gsd-power[12749]: Unable to inhibit suspend: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying Nov 10 00:20:13 lenovo gsd-media-keys[12746]: Unable to inhibit suspend: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying Nov 10 00:20:13 lenovo systemd[1]: Starting SSSD PAM Service responder... Nov 10 00:20:13 lenovo systemd[1]: systemd-logind.service: Main process exited, code=exited, status=1/FAILURE Nov 10 00:20:13 lenovo systemd[1]: systemd-logind.service: Failed with result 'exit-code'. -- Later, I observe that gnome-session cannot communicate with systemd using GDBus and ends up failling back to a "non-systemd procedure": -- Nov 10 00:20:13 lenovo gnome-session[18803]: gnome-session-binary[18803]: WARNING: Failed to upload environment to systemd: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not exist Nov 10 00:20:13 lenovo gnome-session-binary[18803]: WARNING: Failed to upload environment to systemd: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not exist Nov 10 00:20:13 lenovo systemd[12345]: Failed to start GNOME Wacom tablet support service. Nov 10 00:20:13 lenovo systemd[12345]: org.gnome.SettingsDaemon.Power.service: Failed with result 'exit-code'. Nov 10 00:20:13 lenovo systemd[12345]: Failed to start GNOME power management service. Nov 10 00:20:13 lenovo gnome-session[18803]: gnome-session-binary[18803]: WARNING: Failed to reset failed state of units: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not exist Nov 10 00:20:13 lenovo gnome-session-binary[18803]: WARNING: Failed to reset failed state of units: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not exist Nov 10 00:20:13 lenovo gnome-session[18803]: gnome-session-binary[18803]: WARNING: Falling back to non-systemd startup procedure due to error: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not exist Nov 10 00:20:13 lenovo gnome-session-binary[18803]: WARNING: Falling back to non-systemd startup procedure due to error: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not exist -- Could this be a systemd bug? -- 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/1950393 Title: GDM session crashes on suspend on Ubuntu 21.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1950393/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1813441] Re: Can no longer drag and drop files between desktop and applications
@dundir Maybe you're right, I don't know. I just tried to do what I believed is best for Ubuntu, the distro I've been using since 2008 or so: to speak out giving my feedback, hoping it will be heard by the right people. If things won't change I'll look elsewhere, clearly. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1813441 Title: Can no longer drag and drop files between desktop and applications To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1813441/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1813441] Re: Can no longer drag and drop files between desktop and applications
You're failing to understand the concept of "show-stopper" bug, also known as "ship-stopper". The severity of such a bug is so big, that the whole release a product must be postponed, until the bug is fixed. Bugs of this kind are ones that substantially compromise the usability of a product. For example, a bug in a browser's rendering engine that doesn't allow a single major website (social networks, search engines etc.) to render correctly. Millions of people won't use that browser because of that. Another example? A GCC bug that doesn't allow the Linux kernel to compile or, even worse, compiles but generates incorrect instructions and the kernel doesn't boot. Even if that C compiler had a TON of new and cool features and it was 200% faster than its predecessor, would you allow it to be released knowing the you cannot compile Linux? I wouldn't, never. Most of the time, we make trade-offs, both in software development and in release management as well. For example? We've fixed 100 bugs at the price of introducing 5 new ones. That's fine, generally. BUT, some bugs are critical and cannot even be put in the equation. I don't need the whole "decision tree" for that. Such bugs, have priority above everything else combined. The 10,000 new features of KDE 4 were worthless, compared to the fact that it was not stable and crashed the whole time. I wanted so much to use it at the time, because it was so cool and visually pleasing. But, at the end I gave up because of its instability and switched to GNOME. A car is *worthless* if its breaking system doesn't work. A compromise can be made when the breaking system is relatively worse than the one in the previous model, but it's still working, it's still doing an acceptable job. So, how to decide which bugs are show-stoppers? Well, there are user experience people, product managers, VPs etc, but ultimately, such a decision is SUBJECTIVE. I have no "mathematical proof" that this was a show-stopper bug, neither do you that this wasn't. I expressed my opinion, trying to make the Ubuntu leadership to reconsider such decision making. Maybe I failed, maybe I didn't. But if nobody makes criticism, it's almost impossible for the leadership to get a feedback and improve its decision-making. At the end, given users' feedback, I hope Ubuntu leaders will ask themselves: "was that the right call to make?". Maybe, just maybe, the next time they'll be more conservative when releasing an LTS. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1813441 Title: Can no longer drag and drop files between desktop and applications To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1813441/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1813441] Re: Can no longer drag and drop files between desktop and applications
Hi Jonathan, I'm happy to start a dialogue about this issue. 1. It's great to hear that the problem will be fixed in 21.04. Maybe a backport to the 20.04 LTS should be considered as well? 2. I know, I don't have problems with fixing things by myself, per se. I'm irritated that this was not a "corner case" that a few will people will even notice. It's a "show stopper" bug. I'm criticizing the *decision making* here. 3. Yes, I realize that's GNOME's fault. So, the solution was to simply stick to the older version of GNOME, wasn't it? It's a BAD idea to upgrade to the latest version of XYZ, when it's broken, in particular when we're talking about an LTS release, that's supposed to be super- stable. That's simply *bad judgement*. Of course Canonical cannot fix every GNOME bug, I totally agree. I'm a very practical person. Just, don't upgrade the package; it's simple as that. A Linux distribution maintainers' main job is choose carefully which version each software package to include in the distro. The typical questions are: "is the package XYZ stable enough for our release?", "shall we use libxyz 1.23 instead of libxyz 1.22 to fix the problem PR123, but risking to break something else?". Also, did "desktop-icons-ng-ding" exist in 2020 before the release of the LTS? Not a rhetorical question, I honestly don't know. If it did, than the LTS should have included it. Otherwise, the LTS should have just used the older version of GNOME. No matter how you put it, no technical reason justifies breaking this way the user interface. Again, if it were something affecting < 1% of the users, I would have understood. But not in this case. It's not a glitch hidden somewhere, it's one of the first things people notice after installing Ubuntu. I noticed it in a matter of minutes. It's *NOT* a problem of resources, it's a decision-making problem. Vlad -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1813441 Title: Can no longer drag and drop files between desktop and applications To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1813441/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1813441] Re: Can no longer drag and drop files between desktop and applications
Guys, this is a *BRUTAL* regression. It's NOT acceptable to break the desktop experience like that in a LTS release because "the legacy code was unmaintainable". Either replace the legacy code with a mature, well- written extension which works *exactly* the same way, or continue to maintain the old dirty (whatever) code, until you have a VALID replacement. You're *under-estimating* the impact of such a bug. Desktop icons have been "a thing" for the last 30 years or so and are the first thing any user sees. And I'm not talking only about non-technical people: I'm talking about people like me that have been using Linux since 1998. Now, not only arrow keys and drag'n'drop don't work, but even just creating or deleting a file on the desktop causes an ugly refresh. Sometimes, just moving an icon causes the whole gnome shell to crash. I was hoping this bug would be fixed ASAP after the 20.04 release or, at most, for the 20.10 release, but still nothing. And, no, I don't wanna use dirty workarounds which will break on upgrade. I'd like an officially-supported fix. For instabilities like these "the world" stopped using KDE 4 and switched to GNOME. Even MANY years later now, with KDE perfectly stable etc., people still use GNOME. Do you really want to loose the desktop segment? People will stop using Ubuntu for things like that. This bug's "Importance" should be: "VERY HIGH", not "Medium". -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1813441 Title: Can no longer drag and drop files between desktop and applications To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1813441/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1752091] Re: gvfsd-metadata[1703]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed
In my case, the bug apparead when I mounted an Cryptomator volume and began to navigate on it. Ubuntu 18.04 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1752091 Title: gvfsd-metadata[1703]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1752091/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1243659] Re: folder opens when I place mouse without clicking or releasing button. 13.10
Confirm. My mouse behaviour is unpredictable, while touchpad works fine. I have not changes any settings. The problem appears after the upgrade. -- 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/1243659 Title: folder opens when I place mouse without clicking or releasing button. 13.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1243659/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1243806] Re: Folder names in Location area keeps the width (13.10)
That is how it looks like. I can not change the width of any column. ** Attachment added: illustration https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1243806/+attachment/3893539/+files/Screenshot%20from%202013-10-28%2010%3A32%3A01.png -- 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/1243806 Title: Folder names in Location area keeps the width (13.10) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1243806/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1243806] Re: Folder names in Location area keeps the width (13.10)
confirm -- 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/1243806 Title: Folder names in Location area keeps the width (13.10) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1243806/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1107286] [NEW] Unexpected behavior of Nautlius in two-panel mode when open mp3-player or camera.
Public bug reported: Steps to reproduce: 1. Plug in camera/mp3/phone. 2. Launch Nautilus, open ~. 3. Press F3, you'll see two panels of equal widths. 4. Open camera/mp3/phone folder by clicking on it leftward. 5. See how Nautilus increased one panel and decreased another. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: nautilus 1:3.5.90.really.3.4.2-0ubuntu4.1 ProcVersionSignature: Ubuntu 3.5.0-22.34-generic 3.5.7.2 Uname: Linux 3.5.0-22-generic i686 ApportVersion: 2.6.1-0ubuntu9 Architecture: i386 Date: Mon Jan 28 01:23:02 2013 GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b'835x343+401+272' InstallationDate: Installed on 2013-01-25 (2 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release i386 (20121017.2) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 quantal running-unity ** Attachment added: Screenshot from 2013-01-28 01:30:26.png https://bugs.launchpad.net/bugs/1107286/+attachment/3503611/+files/Screenshot%20from%202013-01-28%2001%3A30%3A26.png -- 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/1107286 Title: Unexpected behavior of Nautlius in two-panel mode when open mp3-player or camera. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1107286/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 944624] Re: nautilus crashed with SIGSEGV in mainloop_proxy_func()
Yes, even in the same folder. -- 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/944624 Title: nautilus crashed with SIGSEGV in mainloop_proxy_func() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/944624/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 554636] Re: rhythmbox crashed with SIGSEGV in rb_source_can_pause()
But this bug appears sometimes. -- rhythmbox crashed with SIGSEGV in rb_source_can_pause() https://bugs.launchpad.net/bugs/554636 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 619722] Re: gvfsd-smb crashed with SIGSEGV in free()
I can't reproduce this crash again -- gvfsd-smb crashed with SIGSEGV in free() https://bugs.launchpad.net/bugs/619722 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 624087] Re: nautilus crashed with SIGSEGV in g_cclosure_marshal_VOID__BOXED()
In my case I got this crash after returning from suspend mod -- nautilus crashed with SIGSEGV in g_cclosure_marshal_VOID__BOXED() https://bugs.launchpad.net/bugs/624087 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 394349] Re: nautilus crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()
Crashed when I am trying to search files in nautilus using Ctrl + F. But in my case it was unexpected crash. I can't reproduce it again -- nautilus crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID() https://bugs.launchpad.net/bugs/394349 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 269805] Re: gnome-window-properties gives error about configuration tool not being registered
This bug affects me to. Description:Ubuntu maverick (development branch) Release:10.10 -- gnome-window-properties gives error about configuration tool not being registered https://bugs.launchpad.net/bugs/269805 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 223327] Re: configuration of evolution mail for gmail.com
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/13973071/Dependencies.txt ** Attachment added: ProcMaps.txt http://launchpadlibrarian.net/13973072/ProcMaps.txt ** Attachment added: ProcStatus.txt http://launchpadlibrarian.net/13973073/ProcStatus.txt -- configuration of evolution mail for gmail.com https://bugs.launchpad.net/bugs/223327 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 223327] [NEW] configuration of evolution mail for gmail.com
Public bug reported: Binary package hint: evolution I cannot configure Evolution mail to get get and send my gmail mail. ProblemType: Bug Architecture: i386 Date: Mon Apr 28 00:11:47 2008 DistroRelease: Ubuntu 8.04 ExecutablePath: /usr/bin/evolution Package: evolution 2.22.1-0ubuntu3 PackageArchitecture: i386 ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evolution Uname: Linux 2.6.24-16-generic i686 ** Affects: evolution (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug -- configuration of evolution mail for gmail.com https://bugs.launchpad.net/bugs/223327 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
