Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-software (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-software in Ubuntu.
I'm getting the same error that #4 is getting with a Samsung Galaxy S5
Mini on ubuntu 16.04. Like with OP, disabling USB debugging fixed the
issue.
libmtp error: could not get object handles.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
[Expired for gdm3 (Ubuntu) because there has been no activity for 60
days.]
** Changed in: gdm3 (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
[Expired for Ubuntu GNOME because there has been no activity for 60
days.]
** Changed in: ubuntu-gnome
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
[Expired for Ubuntu GNOME because there has been no activity for 60
days.]
** Changed in: ubuntu-gnome
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
[Expired for gnome-terminal (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: gnome-terminal (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
[Expired for gnome-terminal (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: gnome-terminal (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
FYI I figured out that for me at least, shotwell was stuck in this state
because I needed to unlock my phone and select an item from the
notifications dropdown to enable photo transfer. The notification didn't
show up from the lock screen.
--
You received this bug notification because you are a
I am going to withdraw this bug.
I just realized that the left and right arrows are used to show the
beginning or ending of the path, respectively, when the path is too long
to fit in the horizontal space of the Nautilus header bar.
When the full path doesn't fit:
- Clicking the left arrow
** Information type changed from Private to Public
** Summary changed:
- gnome-shell crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a()
+ gnome-shell crashed with SIGSEGV in
g_type_check_instance_is_fundamentally_a() from g_value_set_object()
--
You received this bug
Curious if this is a one off or being consistently observed. Quite
annoying in my setup since the VM gets powered on/off a fair bit and the
setting refuses to stick.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in
** Tags added: nvidia
--
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/1723678
Title:
Some code accessed the property 'discreteGpuAvailable' on the module
'appDisplay'. | This
** Information type changed from Private to Public
--
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/1723615
Title:
gnome-shell crashed with SIGSEGV in
** Information type changed from Private to Public
--
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/1723620
Title:
gnome-shell crashed with SIGSEGV in
** Tags added: amdgpu
** Summary changed:
- Artfull won't start with wayland activated
+ Artful won't start with Wayland activated
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
This is probably either a bug in the GL code paths of clutter-gst, or
gstreamer-vaapi.
I don't suppose 'mpv' works for you with DVDs?
** Package changed: totem (Ubuntu) => gstreamer-vaapi (Ubuntu)
** Also affects: clutter-gst-3.0 (Ubuntu)
Importance: Undecided
Status: New
** Changed
Workspace to dock isn't in the Ubuntu archive, is it?
https://extensions.gnome.org/extension/427/workspaces-to-dock/
If it's not installed via Ubuntu, and assuming the bug is in the
extension and not in Ubuntu's gnome-shell changes, then this bug would
be invalid for Ubuntu.
** Changed in:
** Summary changed:
-
/usr/bin/gnome-shell:5:g_malloc0:blur_pixels:_st_create_shadow_pipeline:_st_create_shadow_pipeline_from_actor:st_icon_update_shadow_pipeline
+ gnome-shell crashed with SIGTRAP in g_malloc0() from blur_pixels() from
_st_create_shadow_pipeline() from
I recall there were a few different bug reports for this over the last
few months. Although haven't seen one in a while.
--
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/1705458
*** This bug is a duplicate of bug 1706203 ***
https://bugs.launchpad.net/bugs/1706203
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 #1706203, so is being marked as such.
** Tags added: artful
--
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/1706203
Title:
gnome-shell crashed with heap corruption in g_strfreev() from
g_themed_icon_finalize()
*** This bug is a duplicate of bug 1716160 ***
https://bugs.launchpad.net/bugs/1716160
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1716160, so it is being marked as such. Please
Public bug reported:
I have open Firefox, it is maximized. Clicking on it's icon in the Dock
does nothing, I expect it would minimize Firefox. Unity, KDE and Windows
behave in this manor.
Window doesn't have to be maximized to show this behavior, clicking the
icon in the Dock will bring up a
Public bug reported:
I open 2 File manager windows and also have other windows open. From the
side dock, I can switch between the 2 File manager windows. But Alt+Tab
doesn't swap back and forth like expected, it picks some other open
application and brings that to the front.
Tested this with
Public bug reported:
Shotwell would not let my scroll down any further to select some photoss
on the bottom row.
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: shotwell 0.26.3-1ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
** Attachment added: "cannot_scroll_down.png"
https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1723824/+attachment/4972343/+files/cannot_scroll_down.png
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to shotwell in Ubuntu.
Public bug reported:
Opening "Samsung_Android\Card\DCIM\Camera" folder with many images gets
stuck at "Loading..." and never shows anything. I have waited 10
minutes. There is no error and not a single icon shows.
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: nautilus 1:3.26.0-0ubuntu1
This must surely relate to the snapd package - shouldn't it be providing
the .policy file?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1722195
Title:
no policy kit auth
** Branch linked: lp:~ubuntu-desktop/gnome-software/ubuntu
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1723312
Title:
/usr/bin/gnome-
Fix is in lp:~ubuntu-desktop/gnome-software/ubuntu and ppa:ubuntu-
desktop/gnome-software (3.26.1-0ubuntu2~ppa1). Tested by installing
moon-buggy (crashes with archive version, fixed with new version).
Awaiting QA confirmation before release.
The fix is quite simple - it was a NULL pointer access
This regression was introduced with the fix for bug 1718170.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1723312
Title:
/usr/bin/gnome-
*** This bug is a duplicate of bug 1505409 ***
https://bugs.launchpad.net/bugs/1505409
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 #1505409, so is being marked as such.
** Description changed:
Test Case
1. Install a snap package from gnome-software
- 2. When the U1 auth dialog shows up enter your credentials and proceed
+ 2. When the U1 auth dialog shows up enter your credentials and proceed (with
recent snapd you need to cancel the polkit dialog that shows
This seems worthwhile to backport to Ubuntu 16.04.3 LTS.
--
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/1453336
Title:
shotwell fails to import iphone photos
To manage
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1723802
** Tags added: iso-testing
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
0 days ago)
InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Beta i386 (20171015)
InstalledPlugins:
gnome-software-plugin-flatpak N/A
gnome-software-plugin-limba N/A
gnome-software-plugin-snap3.26.1-0ubuntu1
SourcePackage: gnome-software
UpgradeStatus: No upgrade log pre
** Attachment added: "picture showing the error shown"
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1723802/+attachment/4972199/+files/Workspace%201_036.jpg
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
*** This bug is a duplicate of bug 1556601 ***
https://bugs.launchpad.net/bugs/1556601
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 #1556601, so is being marked as such.
-flatpak N/A
gnome-software-plugin-limba N/A
gnome-software-plugin-snap3.26.1-0ubuntu1
LiveMediaBuild: Ubuntu-Budgie 17.10 "Artful Aardvark" - Beta amd64 (20171015)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
SHELL=/bin/bash
SourcePackage: gnom
Probably should note that I eventually got a terminal, I think it was
from Alt+F2 and "sudo apt-get install -y xterm"
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1723571
*** This bug is a duplicate of bug 1718158 ***
https://bugs.launchpad.net/bugs/1718158
** Attachment added: "picture showing the error shown"
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1723790/+attachment/4972142/+files/Workspace%201_035.jpg
** This bug has been
** Tags added: ubuntu-fr-artful
--
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/1723577
Title:
Artfull won't start with wayland activated
To manage notifications about this bug go
Xavier , as a workaround you can use the option nomodeset as boot option
and then disable wayland in custom.conf to start with xorg
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
Same here, all worked fine until 6th October, since 7th impossible to
boot : screen stays frozen at the Ubuntu logo step, nothing works (even
Ctrl Alt F1).
Last line says "Started User Manager for UID 121"
lspci -nn | grep VGA
07:00.0 VGA compatible controller [0300]: Advanced Micro Devices,
The worst thing one can do it so maintain his position instead of apologising
after being rude and being called out on that.
At least one workaround was proposed even in this very thread.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
*** This bug is a duplicate of bug 1679251 ***
https://bugs.launchpad.net/bugs/1679251
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 #1679251, so is being marked as such.
Same error shortly after boot and upgrade (could be coincidental):
Oct 15 15:38:08 XXX dbus-daemon[2685]: Activating service
name='com.intel.dleyna-renderer'
Oct 15 15:38:08 XXX dleyna-renderer-service[5506]: dLeyna core version 0.4.0
Oct 15 15:38:08 XXX dleyna-renderer-service[5506]:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-software (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-software in Ubuntu.
*** This bug is a duplicate of bug 1714989 ***
https://bugs.launchpad.net/bugs/1714989
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 #1714989, so is being marked as such.
Public bug reported:
.
ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.1-0ubuntu3
Uname: Linux 4.13.7-041307-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CrashCounter: 1
Public bug reported:
atualizei da versão 16.04 para 17.04 e agora está apresentando essa
mensagem de erro. O que devo fazer para resolver o problema?
ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: systemd-sysv 232-21ubuntu5
ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17
Adding this to *this* bug, despite the "Fix Released", because it
exactly matches the original post for this bug, whereas the others I've
encountered and reported on are different:
Oct 14 20:02:45 fleetfoot gnome-shell[12750]:
meta_monitor_manager_get_logical_monitor_from_number: assertion
** Changed in: fonts-stix (Ubuntu Wily)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to fonts-stix in Ubuntu.
https://bugs.launchpad.net/bugs/1487148
Title:
[MIR] fonts-stix -- to replace xfonts-mathml
** Changed in: ubuntu-jp-improvement
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1723358
Title:
gnome-settings-daemon
** Changed in: systemd (Ubuntu Wily)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1502097
Title:
packages fail to install/upgrade: Connection
@Marco:
sudo gdb -p $(gnome-shell)
org.gnome.Shell already exists on bus and --replace not specified
gdb: option '-p' requires an argument
Use `gdb --help' for a complete list of options.
Should I add --replace?
--
You received this bug notification because you are a member of Ubuntu
Desktop
@Laney / release team: To gain time, and since I hope there is still
time for this to make it to the ISO, I have uploaded an im-config change
to the unapproved queue, even if there was no preceding approval from
the release-team. Hope this is considered ok.
** Changed in: im-config (Ubuntu)
*** This bug is a duplicate of bug 1556601 ***
https://bugs.launchpad.net/bugs/1556601
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 #1556601, so is being marked as such.
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1723571
** Tags added: iso-testing
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-terminal (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu.
Rather a GDM bug. I it doesn't get stuck on Plymouth, it starts up the
“Ubuntu“ gnome-shell session reliably for me.
** Package changed: gnome-shell (Ubuntu) => gdm3 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in
If I get past Plymouth and into GDM (I have to try 4 times to succeed),
I can log into the “Ubuntu“ session reliably. So I think that this bug
is rather a GDM one than a gnome-shell one.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
For me it worked reliably the whole development cycle until the week
leading up to the 7th of October. It is borked just for about a week
now. On the 5th of October I remember it being fine, it was borked when
starting Ubuntu up on the morning of October 7th.
Now it seems like a dealbreaker worth
Even after the updates of today (with the new kernel and the gnome-shell
crash fix) the boot splash is getting stuck most of the time (certainly
3 out of 4 tries).
Only switching to the nvidia 340 blob fixes that (then it boots
reliably, not showing Plymouth at all).
I don't think that it is a
74 matches
Mail list logo
