** Tags removed: stop-ship
--
Error while copying mounts
https://bugs.launchpad.net/bugs/261484
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
Public bug reported:
Binary package hint: gnome-keyring
In Hardy, gnome-keyring is launched via dBus as opposed to being exec'd
directly by gnome-session as in Gustsy.
The dBus conf file for gnome-keyring (
/usr/share/dbus-1/services/org.gnome.keyring.service ) specifies the
--foreground option
** Attachment added: Enable logging even if --foreground is spec'd
http://launchpadlibrarian.net/12630118/70_enable_logging.patch
--
logging disabled if --foreground used
https://bugs.launchpad.net/bugs/201797
You received this bug notification because you are a member of Ubuntu
Desktop
I'm probably going to have to spin a special version for the Mobile PPA
( for this bug, and pre-populating a default password-less keyring )
anyways, so yes, I can wait for the version update. Backporting the fix
however might help with future debugging of desktop keyring problems.
Your call...
I think the check is whether an *encrypted* keyring is being used. If
the keyring already has a NULL password, and is in the clear, then
nothing needs to be displayed.
An alternative to actually changing the key directly would be an
explanation of what needs to be changed, additional words about
I just ran into this running UNR Jaunty on a netbook with a 1024x576
screen which seems to be the resolution most of the smaller netbooks are
shipping with now. I think if we chose this resolution as our smallest
target, we'd be in good shape.
--
gdmsetup dialog is to big for 1024 x 768
** Changed in: oem-priority
Status: New = Confirmed
** Changed in: oem-priority
Importance: Undecided = High
--
Video out hot key sends super + p + return on many upcoming Dell HP systems
https://bugs.launchpad.net/bugs/539477
You received this bug notification because you are a
Closing out the Dell project task, as it's used to track non-public HW
enablement work.
** Changed in: dell
Status: In Progress = Won't Fix
--
[Feature Request] Add Service Tag and support URL in System Monitor under
System
https://bugs.launchpad.net/bugs/332060
You received this bug
Please do not add bug tasks to the Dell project. This project is used
to track internal fixes for factory-related hardware enablement.
** Changed in: dell
Status: New = Invalid
--
Battery life estimation always show estimating... in battery (indicator
applet)
I'm assuming this is for Karmic, correct?
Can you also name a currently available machine that this bug can easily
be reproduced on? Can you describe how the machine supports multiple
outputs ( ie. does it actually have 3, 6, 7, or 8 analog outputs, or are
these digital output modes )?
As of
Once we flesh out more of the details of this bug, we should also
solicit an opinion from upstream too.
--
Pulse audio control panel does not allow for 3, 5.1, 6.1, 7.1 speaker multi
channel audio if supported by sound card
https://bugs.launchpad.net/bugs/440253
You received this bug
Again, *if* the low-level ALSA reporting is correct, then usable HW
profiles should've been generated. These should include multi-channel
output profiles, although I'm not sure if 6.1 and 7.1 are supported. If
the correct ALSA controls are not exposed for a particular OEM's
machine, then
Public bug reported:
Binary package hint: gnome-settings-daemon
e...@zappa:% lsb_release -rd
Description:Ubuntu karmic (development branch)
Release:9.10
gnome-settings-daemon 2.27.4-0ubuntu1
While testing both blueman and gnome-bluetooth, I've managed to crash
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/29620368/Dependencies.txt
--
gnome-settings-daemon crashes when re-connecting Sound Output to BT device
https://bugs.launchpad.net/bugs/405839
You received this bug notification because you are a member of Ubuntu
Desktop
Here's the backtrace.
Exact steps to reproduce:
1. install gnome-bluetooth
2. pair connect to an audio headset ( in my case a samsung snh500 )
3. change sound output to bt via the sound applet : preferences : output
tab
4. play some music ( in this case via rhythmbox )
5. stop playback
6.
** Attachment added: gdb settings-daemon backtrace
http://launchpadlibrarian.net/29624391/gdb-gsd.txt
--
gnome-settings-daemon crashes when re-connecting Sound Output to BT device
https://bugs.launchpad.net/bugs/405839
You received this bug notification because you are a member of Ubuntu
I'm not sure how I could've done so ( send the bug via apport )? The
system didn't seem to detect the crash, so I had to manually run
'ubuntu-bug', and thus it looks like it only attached Dependencies.txt.
I don't fully understand how ubuntu-bug works, but do recall that it
hooks into apport.
Yes, apport is enabled.
Yes, there's a crash for gnome-settings-daemon in /var/crash now.
I can re-run to get another one if necessary.
--
gnome-settings-daemon crashes when re-connecting Sound Output to BT device
https://bugs.launchpad.net/bugs/405839
You received this bug notification
I managed to hit this bug by:
1. install gnome-bluetooth
2. pair connect to an audio headset ( in my case a samsung snh500 )
3. change sound output to bt via the sound applet : preferences : output
tab
4. play some music ( in this case via rhythmbox )
5. stop playback
6. toggle sound output
*** This bug is a duplicate of bug 404538 ***
https://bugs.launchpad.net/bugs/404538
** This bug has been marked a duplicate of bug 404538
gnome-settings-daemon crashed with SIGSEGV in gvc_mixer_stream_is_running()
--
gnome-settings-daemon crashes when re-connecting Sound Output to BT
Sure, I'll give it a try...
--
gnome-settings-daemon crashed with SIGSEGV in gvc_mixer_stream_is_running()
https://bugs.launchpad.net/bugs/404538
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
I grabbed the specified commit and rebuilt using the latest bzr branch (
eg. 2.27.5-0ubuntu1 ). This seems to fix the problem, I can't get the
crash to occur anymore.
I created a topic branch which contains the new patch, I'll add it to
the bug.
Please let me know if you'd like to propose it as
OK, false positive... the patch in fact doesn't build. I guess I need
more than just the single commit.
--
gnome-settings-daemon crashed with SIGSEGV in gvc_mixer_stream_is_running()
https://bugs.launchpad.net/bugs/404538
You received this bug notification because you are a member of Ubuntu
For now, I just modifed the /plugins/media-keys/cut-n-paste/Makefile.in
to add the new files. It may not be the right way to do it, but it's
gotten me to the point where I'm testing the new code...
--
gnome-settings-daemon crashed with SIGSEGV in gvc_mixer_stream_is_running()
So I'm still getting the crash with the new code.
I tried to pin down the exact crash using g_assert g_warning
statements, but wasn't successful.
So, one question I have, is how do I easily create a debug version of
this code?
I tried adding:
DEB_BUILD_OPTIONS=debug nostrip nooopt to the
It looks like the GvcMixerStream gets unref'd whilst it's still the
default sink.
I attached to gsd using gdb, and caught the crash:
Program received signal SIGSEGV, Segmentation fault.
gvc_mixer_stream_is_running (stream=0x6de170) at gvc-mixer-stream.c:679
679 if
I just hit this running the lastest version of pulse ( 9.0.16-test4 )
and gnome-media ( 2.27.5-0ubuntu1 ), and gnome-bluetooth (
2.27.8-0ubuntu1 ).
I paired my Samsung SBH500 BT headset.
I'm running on a new 15 Macbook. I paired the headset, went to Sound
Properties Hardware tab, enabled the BT
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/30007623/Dependencies.txt
** Tags added: apport-collected
--
gnome-volume-control crashed with SIGSEGV in g_closure_invoke()
https://bugs.launchpad.net/bugs/384524
You received this bug notification because you are a member
Architecture: amd64
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: wl nvidia
Package: gnome-media 2.27.5-0ubuntu1
PackageArchitecture: amd64
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, user)
LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-5.24-generic
Uname: Linux 2.6.31-5-generic x86_64
Re-tested with gnome-media 2.27.90-0ubuntu1 ( which includes the commit
referenced in the upstream Gnome bug which fixes a problem with an un-
initialized variable ), I can no longer reproduce the crash.
--
gnome-volume-control crashed with SIGSEGV in g_closure_invoke()
Two things...
1. If possible, please try and use an Ethernet connection to update your
system to the latest greatest Karmic updates.
2. If you're able to get the system online, then please run the
following command from a terminal ( or use Alt-F2 / Run Application ):
apport-collect 408911
Public bug reported:
During UDS-P I was experimenting with various settings to reduce power
consumption on my Lenonvo Thinkpad 410s.
I turned Bluetooth off via the System Settings - Bluetooth panel. I
also removed the icon from the panel by turning visibility to Off.
This all works great except
apport information
** Tags added: apport-collected oneiric running-unity
** Description changed:
During UDS-P I was experimenting with various settings to reduce power
consumption on my Lenonvo Thinkpad 410s.
I turned Bluetooth off via the System Settings - Bluetooth panel. I
also
Looks like my apport-collect didn't really grab too much more
information...
Here's the output from 'rfkill list':
espy@zappa:% sudo rfkill list
[sudo] password for espy:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
No BT rfkill device is listed...
--
You received
So I may have a bit of mud on my face...
There may not be an actual BT adapter in this machine, however to save
some face, the BT icon was shown on the panel and I did run the settings
app to disable/remove it from the panel. I'm pretty I toggled both
switches at the time.
I've checked 'lsusb',
I'm pretty sure it was from the indicator... but again this was six
months back.
If I get a chance later today, I can check with a LiveCD.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-bluetooth in Ubuntu.
Based upon my comment #4 which states that 'lsusb' doesn't show a
Bluetooth adapter, and the fact that after I recently got my system
board replaced and it now does show a Bluetooth adapter, I'm going to
mark this bug as invalid.
** Changed in: gnome-bluetooth (Ubuntu)
Status: New =
So I think this bug should be split into two different bugs.
First, the original reporter filed this on an x86 machine running
Desktop, not Touch.As urfkill is still not used on the Desktop as of
the latest utopic images, I'm splitting this into a urfkill bug for the
problems described by
@Thomas
What's the client component in this case, and why wasn't it responding?
Also, does this still tie into the WiFi state per the original
description?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to location-service in Ubuntu.
And some more details, by adding 'env QDBUS_DEBUG=1' to the unity8
upstart job, I'm getting a lot more detail without having to further
modify the code.
I'm seeing "Adding rule" log statements produced by
QDBusConnectionPrivate, but no corresponding "Removing rule" logs, so
sounds like my
** Branch linked: lp:~phablet-team/network-manager/lp1480877-wifi-rm-
dup-scan-signals
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to location-service in Ubuntu.
https://bugs.launchpad.net/bugs/1480877
Title:
Access points'
** Also affects: location-service (Ubuntu)
Importance: Undecided
Status: New
** Changed in: location-service (Ubuntu)
Status: New => Incomplete
** Changed in: network-manager (Ubuntu)
Status: Incomplete => In Progress
--
You received this bug notification because you
: New => In Progress
** Changed in: network-manager (Ubuntu RTM)
Assignee: (unassigned) => Tony Espy (awe)
** Changed in: network-manager (Ubuntu)
Importance: Undecided => High
** Changed in: network-manager (Ubuntu RTM)
Importance: Undecided => High
--
You recei
Note, one other observation noticed this week. If the HERE Maps
application is running and WiFi is enabled, it triggers scans every
4-5s.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to location-service in Ubuntu.
** Changed in: network-manager (Ubuntu RTM)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to location-service in Ubuntu.
https://bugs.launchpad.net/bugs/1480877
Title:
Access points'
@Markcortbass
Do you have the latest OTA installed?
Which app were you using when you hit the bug?
Also, it's possible that bug #1480877 might have something to do with
this, as when WiFi is enabled, and HERE Maps is run, a new WiFi scan is
triggered every 4-5s, and the resulting spike in DBus
Just a quick update to mention that the change to the NM bearer plugin
seems to have caused a regression when qtbase is installed from the PPA
onto a desktop ( for UI development work ).
To reproduce, the overlay PPA needs to be added as a software source,
then ubuntu-system-settings
The latest version of the patch is now in a silo-026, included as part
of a new qtbase version 5.4.1+dfsg-2ubuntu11~vivid1.
** Changed in: qtbase-opensource-src (Ubuntu)
Status: In Progress => Fix Committed
** Changed in: sync-monitor (Ubuntu RTM)
Status: New => Incomplete
--
You
The associated version for the dbus-cpp in silo-026 is:
4.3.0+15.04.20151126-0ubuntu1
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to dbus-cpp in Ubuntu.
https://bugs.launchpad.net/bugs/1480877
Title:
Access points'
The fix has landed in silo-026, as part of location-services version:
2.1+15.04.20151202.1-0ubuntu1
** Changed in: location-service (Ubuntu RTM)
Status: In Progress => Fix Committed
** No longer affects: sync-monitor (Ubuntu RTM)
** No longer affects: maliit-framework (Ubuntu RTM)
** No
@Selene
Just wanted to confirm that we don't need any more investigation re:
your comment #131 ( I think that may be the largest comment # I've seen
in a LP bug ), as your latest update to bug #1524133 indicated that
you'd isolated the problem to a SIM with an expired data plan?
@Timo
We should
hanged in: qtbase-opensource-src (Ubuntu RTM)
Status: New => Fix Released
** Changed in: qtbase-opensource-src (Ubuntu RTM)
Assignee: (unassigned) => Tony Espy (awe)
** Changed in: qtbase-opensource-src (Ubuntu RTM)
Importance: Undecided => High
** Changed in: qtbase-opensou
So the latest changes in Lorn's signals6 patch can be summarized as:
1) remove QNetworkManagerEngine::requestUpdate (), which is a public
method which can trigger a WiFi scan request to NM.
This method doesn't appear to be called internally by the bearer plugin,
so if we think extra WiFi scans
Here's my updated patch, the only difference is that it includes a
DBusConnection disconnect() call in the destructor for
QNetworkManagerInterfaceDeviceModem(), which I'd punted on for
expediency while testing earlier this week.
If doesn't include the IPv6 related fix, as this was fixed in NM
Note, I've also pushed a new version based on your latest patch to my
PPA if anyone's interested in testing before it lands in silo-026:
https://launchpad.net/~awe/+archive/ubuntu/ppa
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
@Lorn
Thanks for the update.
I usually do all my testing on rc-proposed, as it's latest and greatest.
I wasn't aware of the "ubuntu-developer" channel. I've tested on rc-
proposed/bq-aquaris.en ( #188 ) with the full set of packages from
silo-026, and everything seemed good to me.
Thar said,
@Lorn
Can you add some details regarding what image channel you actually used
and device for testing? rc-proposed is probably the best base for you
to use.
The "GetAll" behavior you're describing is similar to what I was seeing
with the AccessPoint objects. The code would see a
@Timo
As previously mentioned, I'd like to get this change out as a hot-fix,
and then do proper evaluation of the new connectivity API based plugin
with the goal to land it as part of OTA9.
@Lorn
I'll take a look at that the line you mentioned, however we need to draw
the line at some point and
Just a quick update on my debugging.
I've verified that the NM bearer plugin's qnetworkmanagerengine class is
receiving the 'AccessPointRemoved', is matching them correctly in it's
saved list, and is called delete on the
QNetworkManagerInterfaceAccessPoint instance. The associated destructor
is
Note, QNetworkManagerEngine::setupConfigurations() is also suspect as it
can get called from a couple of places and has a loops over the current
devices and calls deviceAdded().
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to dbus-cpp
Some more details:
- the version of the qtbase package in touch atm is: 5.4.1+dfsg-
2ubuntu10
- I checked and didn't see significant differences in the networkmanager
bearer plugin when comparing against 5.5.1, and 5.6.
- That said, there's been quite a few changes in the QDBus code,
** Changed in: qtbase-opensource-src (Ubuntu)
Assignee: (unassigned) => Tony Espy (awe)
** Changed in: qtbase-opensource-src (Ubuntu)
Importance: Undecided => High
** Changed in: qtbase-opensource-src (Ubuntu)
Status: Confirmed => In Progress
--
You received
I grabbed your patch and incorporated most of it into my latest patch (
I left out a few of the disconnect calls for some of the other NM
interfaces not directly involved in the match rules problem ), however
it failed to build...
While trying to just pull in the pieces and resolve the conflicts
Here's a new version of the patch with all the access-point related
signals removed.
It makes no sense for any of this logic to be present in our system, as
none of our code attempts to control the network configuration via
Bearer Mgmt. With this patch, the plugin will never receive any NM
@Lorn
Thanks for the updated patch.
The only significant difference besides the DeviceModem destructor fix
was the change you mentioned about default routes. Is there a touch-
specific bug that this fixes? On our system, the modem connection will
never be IPv6, whereas it is possible to get a
@Mike
Small stutters when transitioning from mobile to WiFi or visa versa, or
stutters when scanning. The fixes to location-services and Qt both are
applicable to the latter case only...
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
@Lorn
Did you see this recently? If so, what device and image?
As I mentioned, the mobile connection on touch doesn't support IPv6
connections.There was a bug in NM that falsely reported that a
default IPv6 route was available, but this was fixed awhile back.
Please see bug #1444162 for
Re-opened, as there's some interest from OEMs in seeing NM teaming
support land in 18.04.
** Description changed:
Availability:
The package is available in universe, built on all architectures.
Rationale:
- The package is a new (Build-)Depends for network-manager, for network device
68 matches
Mail list logo
