[Bug 1304500] Re: Indicator Test Plan QA Review
** Changed in: indicator-network (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1304500 Title: Indicator Test Plan QA Review To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-bluetooth/+bug/1304500/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1368524] Re: /usr/lib/arm-linux-gnueabihf/indicator-network/indicator-network-service:11:__GI___pthread_mutex_lock:_dbus_platform_rmutex_lock:_dbus_lock:dbus_message_cache_shutdown:dbus_shutdown
no new reports in errors.u.c since October. closing. ** Changed in: dbus-cpp (Ubuntu) Status: New = Fix Released ** Changed in: indicator-network (Ubuntu) Status: New = Fix Released -- 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/1368524 Title: /usr/lib/arm-linux-gnueabihf/indicator-network/indicator-network- service:11:__GI___pthread_mutex_lock:_dbus_platform_rmutex_lock:_dbus_lock:dbus_message_cache_shutdown:dbus_shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus-cpp/+bug/1368524/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1382595] Re: [TOPBLOCKER] /usr/lib/arm-linux-gnueabihf/indicator-network/indicator-network-service:indicator-network-service: pthread_mutex_lock.c:80: __pthread_mutex_lock: Assertion `mutex-__da
based in the ofono and urfkill bugs linked to the #1388065 I would say these are not related. -- 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/1382595 Title: [TOPBLOCKER] /usr/lib/arm-linux-gnueabihf/indicator-network/indicator- network-service:indicator-network-service: pthread_mutex_lock.c:80: __pthread_mutex_lock: Assertion `mutex-__data.__owner == 0' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/dbus-cpp/+bug/1382595/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1382595] Re: [TOPBLOCKER] /usr/lib/arm-linux-gnueabihf/indicator-network/indicator-network-service:indicator-network-service: pthread_mutex_lock.c:80: __pthread_mutex_lock: Assertion `mutex-__da
** Changed in: indicator-network (Ubuntu) Assignee: Antti Kaijanmäki (kaijanmaki) = Thomas Voß (thomas-voss) -- 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/1382595 Title: [TOPBLOCKER] /usr/lib/arm-linux-gnueabihf/indicator-network/indicator- network-service:indicator-network-service: pthread_mutex_lock.c:80: __pthread_mutex_lock: Assertion `mutex-__data.__owner == 0' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/dbus-cpp/+bug/1382595/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1382595] Re: [TOPBLOCKER] /usr/lib/arm-linux-gnueabihf/indicator-network/indicator-network-service:indicator-network-service: pthread_mutex_lock.c:80: __pthread_mutex_lock: Assertion `mutex-__da
** Also affects: indicator-network (Ubuntu RTM) Importance: Undecided Status: New ** Changed in: indicator-network (Ubuntu RTM) Importance: Undecided = Critical ** Changed in: indicator-network (Ubuntu RTM) Status: New = In Progress -- 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/1382595 Title: [TOPBLOCKER] /usr/lib/arm-linux-gnueabihf/indicator-network/indicator- network-service:indicator-network-service: pthread_mutex_lock.c:80: __pthread_mutex_lock: Assertion `mutex-__data.__owner == 0' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/dbus-cpp/+bug/1382595/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1382595] Re: [TOPBLOCKER] /usr/lib/arm-linux-gnueabihf/indicator-network/indicator-network-service:indicator-network-service: pthread_mutex_lock.c:80: __pthread_mutex_lock: Assertion `mutex-__da
Looking at the stacktrace, the assertion error happens inside dbus-cpp worker thread that has called core::dbus::Bus::run(). Some quick googling: http://stackoverflow.com/questions/1105745/pthread-mutex-assertion-error ** Also affects: dbus-cpp Importance: Undecided Status: New ** Changed in: dbus-cpp Status: New = Confirmed ** Also affects: dbus-cpp (Ubuntu) Importance: Undecided Status: New ** Also affects: dbus-cpp (Ubuntu RTM) Importance: Undecided Status: New ** Changed in: dbus-cpp (Ubuntu) Status: New = Confirmed ** Changed in: dbus-cpp (Ubuntu RTM) Status: New = Confirmed ** Changed in: dbus-cpp (Ubuntu) Importance: Undecided = Critical ** Changed in: dbus-cpp (Ubuntu RTM) Importance: Undecided = Critical ** Changed in: dbus-cpp (Ubuntu) Assignee: (unassigned) = Thomas Voß (thomas-voss) ** Changed in: dbus-cpp (Ubuntu RTM) Assignee: (unassigned) = Thomas Voß (thomas-voss) ** Changed in: indicator-network (Ubuntu) Status: Confirmed = Invalid -- 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/1382595 Title: [TOPBLOCKER] /usr/lib/arm-linux-gnueabihf/indicator-network/indicator- network-service:indicator-network-service: pthread_mutex_lock.c:80: __pthread_mutex_lock: Assertion `mutex-__data.__owner == 0' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/dbus-cpp/+bug/1382595/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1382595] Re: [TOPBLOCKER] /usr/lib/arm-linux-gnueabihf/indicator-network/indicator-network-service:indicator-network-service: pthread_mutex_lock.c:80: __pthread_mutex_lock: Assertion `mutex-__da
i-network needs a rebuild as well. ** Changed in: indicator-network (Ubuntu) Status: Invalid = Triaged -- 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/1382595 Title: [TOPBLOCKER] /usr/lib/arm-linux-gnueabihf/indicator-network/indicator- network-service:indicator-network-service: pthread_mutex_lock.c:80: __pthread_mutex_lock: Assertion `mutex-__data.__owner == 0' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/dbus-cpp/+bug/1382595/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1380736] Re: showing notification right after boot causes unity8 crash
** Summary changed: - Unlocking sim causes unity8 crash + showing notification right after boot causes unity8 crash -- 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/1380736 Title: showing notification right after boot causes unity8 crash To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-network/+bug/1380736/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1380736] Re: Unlocking sim while dash is not loaded leads to a system lockup
Might be the same issue: https://errors.ubuntu.com/problem/f53968407e05846ce6dd99e01d5c27df7589b9eb Although the retrace has failed just looking at the signatures makes me think of uncaught exception. At least in i-network we had to guard all calls to core::dbus::Bus::run() inside try-catches as run() sometimes leaks exceptions. ** Also affects: dbus-cpp (Ubuntu) Importance: Undecided Status: New ** Also affects: media-hub (Ubuntu) Importance: Undecided Status: New -- 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/1380736 Title: Unlocking sim while dash is not loaded leads to a system lockup To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-network/+bug/1380736/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1380736] Re: Unlocking sim while dash is not loaded leads to a system lockup
looking at the report mterry posted it looks like coming from qtubuntu-
media. I'm not familiar with that code base but after having a quick
look these caught my eye:
http://bazaar.launchpad.net/~phablet-team/qtubuntu-
media/trunk/view/head:/src/aal/aalmediaplayerservice.cpp:
AalMediaPlayerService::AalMediaPlayerService(QObject *parent):
...
m_service = this;
---
m_hubPlayerSession-playback_status_changed().connect(
std::bind(AalMediaPlayerService::onPlaybackStatusChanged, this,
_1));
...
First m_service is static, so if ever more than one instance of
AalMediaPlayerService is created things will brobably break. Should that
be a singleton instead?
secondly, there is is connection made to m_hubPlayerSession, but it is
not disconnected in
void
AalMediaPlayerService::setPlayer(const
std::shared_ptrcore::ubuntu::media::Player player)
{
m_hubPlayerSession = player;
}
nor in the destructor ~AalMediaPlayerService() even though the (static)
m_service might get descructed as it's parent is relayed to it's parent
QObject class.
** Also affects: qtubuntu-media (Ubuntu)
Importance: Undecided
Status: New
--
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/1380736
Title:
Unlocking sim while dash is not loaded leads to a system lockup
To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-network/+bug/1380736/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1368519] Re: /usr/lib/arm-linux-gnueabihf/indicator-network/indicator-network-service:6:__gnu_cxx::__verbose_terminate_handler:__cxxabiv1::__terminate:std::terminate:__cxxabiv1::__cxa_throw:std::
** Changed in: dbus-cpp (Ubuntu) Status: New = Confirmed ** Changed in: dbus-cpp (Ubuntu) Importance: Undecided = Critical ** Changed in: dbus-cpp (Ubuntu) Assignee: (unassigned) = Thomas Voß (thomas-voss) -- 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/1368519 Title: /usr/lib/arm-linux-gnueabihf/indicator-network/indicator-network- service:6:__gnu_cxx::__verbose_terminate_handler:__cxxabiv1::__terminate:std::terminate:__cxxabiv1::__cxa_throw:std::__throw_system_error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus-cpp/+bug/1368519/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1368524] Re: /usr/lib/arm-linux-gnueabihf/indicator-network/indicator-network-service:11:__GI___pthread_mutex_lock:_dbus_platform_rmutex_lock:_dbus_lock:dbus_message_cache_shutdown:dbus_shutdown
** Also affects: dbus-cpp (Ubuntu) Importance: Undecided Status: New -- 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/1368524 Title: /usr/lib/arm-linux-gnueabihf/indicator-network/indicator-network- service:11:__GI___pthread_mutex_lock:_dbus_platform_rmutex_lock:_dbus_lock:dbus_message_cache_shutdown:dbus_shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus-cpp/+bug/1368524/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1329226] [NEW] com.ubuntu.touch.network.flightMode should be removed
Public bug reported: This key is unused once proper flightmode support lands to system settings. https://code.launchpad.net/~unity-api-team/ubuntu-system-settings/flightmode/+merge/222907 ** Affects: gsettings-ubuntu-touch-schemas (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gsettings-ubuntu-touch-schemas in Ubuntu. https://bugs.launchpad.net/bugs/1329226 Title: com.ubuntu.touch.network.flightMode should be removed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gsettings-ubuntu-touch-schemas/+bug/1329226/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1294780] [NEW] should throw something if trying to write to readonly property
Public bug reported: Currently if set() is called a readonly dbus property the following is printed to the console: Property is not writable IMO an exception should be thrown to help to catch the exact location of the error. ** Affects: dbus-cpp (Ubuntu) Importance: Undecided Status: New -- 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/1294780 Title: should throw something if trying to write to readonly property To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus-cpp/+bug/1294780/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1274701] [NEW] dbus::Signal::disconnect() does not work.
Public bug reported:
This fails:
auto con = signal-connect([this](){});
signal-disconnect(con);
with:
/usr/include/core/dbus/impl/signal.h:185: error: return-statement with a value,
in function returning 'void' [-fpermissive]
return d-handlers.erase(token);
^
** Affects: dbus-cpp (Ubuntu)
Importance: Undecided
Status: New
--
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/1274701
Title:
dbus::Signal::disconnect() does not work.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus-cpp/+bug/1274701/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1272105] [NEW] libdbus-cpp-dev does not debend on libdbus-1-dev
Public bug reported: trying to build a project in jenkins which build-depends on libdbus-cpp- dev fails. In file included from /usr/include/core/dbus/message.h:21:0, from /usr/include/core/dbus/bus.h:23, from /tmp/buildd/connectivity-cpp-0.0.1/dbus-cpp/services/nm.h:21, from /tmp/buildd/connectivity-cpp-0.0.1/src/platform/nmofono/manager.h:24, from /tmp/buildd/connectivity-cpp-0.0.1/src/platform/nmofono/manager.cpp:20: /usr/include/core/dbus/argument_type.h:25:23: fatal error: dbus/dbus.h: No such file or directory #include dbus/dbus.h ^ ** Affects: dbus-cpp (Ubuntu) Importance: Undecided Status: New -- 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/1272105 Title: libdbus-cpp-dev does not debend on libdbus-1-dev To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus-cpp/+bug/1272105/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1272191] [NEW] libdbus-cpp-dev does not depend on dbus
Public bug reported: core::dbus::testing::Fixture requires dbus-daemon to be available but libdbus-cpp-dev does not depend on it. When trying to run a test under CI without dbus-daemon the following exception is thrown: C++ exception with description Session: Could not read address of bus instance. thrown in the test fixture's constructor. either A) libdbus-cpp-dev must depend on package dbus as the Fixture needs it or B) the Fixture should check that dbus-daemon is available and print error message stating that no such command to make it obvious that the package using the Fixture needs to pull it it explicitly. Maybe it would be good idea to print the exact error coming from the system when Fixture tries to execute the command. That would clearly state dbus-daemon: command not found ** Affects: dbus-cpp (Ubuntu) Importance: Undecided Status: New -- 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/1272191 Title: libdbus-cpp-dev does not depend on dbus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus-cpp/+bug/1272191/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1270843] [NEW] D-Bus byte should be std::uint8_t
Public bug reported: http://dbus.freedesktop.org/doc/dbus-specification.html#basic-types : Conventional name: BYTE ASCII type-code: y (121) Encoding: Unsigned 8-bit integer Currently dbus-cpp defines the byte as signed std::int8_t. This should be changed to std::uint8_t. Unfortunately this will break (compilation of) any existing code using the signed byte. ** Affects: dbus-cpp (Ubuntu) Importance: Undecided Status: Confirmed ** Changed in: dbus-cpp (Ubuntu) Status: New = Confirmed -- 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/1270843 Title: D-Bus byte should be std::uint8_t To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus-cpp/+bug/1270843/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1048585] Re: power statistics dialog not centered inside unity-greeter
Did this go in to beta2 or not? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1048585 Title: power statistics dialog not centered inside unity-greeter To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-power/+bug/1048585/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 777712] Re: password dialog doesn't appear when screensaver ends
Are you using multiple monitors (laptop lcd + external for example)? At least for me the password dialog appears sometimes in wrong (detached) display. Also I sometimes have witnessed dialog not being shown on single display setup, but when I enter my password to this non-visible dialog I can still unlock the desktop. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/12 Title: password dialog doesn't appear when screensaver ends To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/12/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 562061] [NEW] screensaver activates inactive display
Public bug reported: Binary package hint: gnome-screensaver I have my laptop attached to a KVM switch and I use the VGA output as my primary desktop on external display. The laptop is below my table with lid closed. I have deactivated the laptops LCD panel from gnome-display- properties. After I upgraded to lucid I noticed that I sometimes lost the upper and lower gnome panels. They just disappeared and I could not get them back without restarting my machine. Then I realized that the panels disappeared after gnome-screensaver had locked the screen for a while. I then had an idea to check the display properties and I noticed that my inactive LCD panel had been activated and thus my primary desktop had been moved to the LCD panel of the laptop (lid closed under my desk) and the panels were there. Now, the easy work-around is to hit alt+F2 after the screensaver has been unlocked, type gnome-display-properties and deactivate the LCD panel. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: gnome-screensaver 2.30.0-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.32-20.29-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-20-generic i686 Architecture: i386 Date: Tue Apr 13 09:34:35 2010 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None ProcEnviron: LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: gnome-screensaver WindowManager: metacity ** Affects: gnome-screensaver (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 lucid -- screensaver activates inactive display https://bugs.launchpad.net/bugs/562061 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 562061] Re: screensaver activates inactive display
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/43998082/Dependencies.txt ** Attachment added: GconfGnomeLockdown.txt http://launchpadlibrarian.net/43998083/GconfGnomeLockdown.txt ** Attachment added: GconfGnomePowerManager.txt http://launchpadlibrarian.net/43998084/GconfGnomePowerManager.txt ** Attachment added: GconfGnomeScreensaver.txt http://launchpadlibrarian.net/43998085/GconfGnomeScreensaver.txt ** Attachment added: GconfGnomeSession.txt http://launchpadlibrarian.net/43998086/GconfGnomeSession.txt ** Attachment added: XorgLog.gz http://launchpadlibrarian.net/43998087/XorgLog.gz ** Attachment added: XorgLogOld.gz http://launchpadlibrarian.net/43998088/XorgLogOld.gz ** Description changed: Binary package hint: gnome-screensaver I have my laptop attached to a KVM switch and I use the VGA output as my primary desktop on external display. The laptop is below my table with lid closed. I have deactivated the laptops LCD panel from gnome-display- properties. After I upgraded to lucid I noticed that I sometimes lost the upper and lower gnome panels. They just disappeared and I could not get them back without restarting my machine. Then I realized that the panels disappeared after gnome-screensaver had locked the screen for a while. I then had an idea to check the display properties and I noticed that my inactive LCD panel had been activated and thus my primary desktop had been moved to the LCD panel of the laptop (lid closed under my desk) and the panels were there. - Now, the easy work-around is to his ctrl+F2 after the screensaver has - been unlocked, type gnome-display-properties and deactivating the LCD + Now, the easy work-around is to hit ctrl+F2 after the screensaver has + been unlocked, type gnome-display-properties and deactivate the LCD panel. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: gnome-screensaver 2.30.0-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.32-20.29-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-20-generic i686 Architecture: i386 Date: Tue Apr 13 09:34:35 2010 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None ProcEnviron: - LANG=en_US.utf8 - SHELL=/bin/bash + LANG=en_US.utf8 + SHELL=/bin/bash SourcePackage: gnome-screensaver WindowManager: metacity ** Description changed: Binary package hint: gnome-screensaver I have my laptop attached to a KVM switch and I use the VGA output as my primary desktop on external display. The laptop is below my table with lid closed. I have deactivated the laptops LCD panel from gnome-display- properties. After I upgraded to lucid I noticed that I sometimes lost the upper and lower gnome panels. They just disappeared and I could not get them back without restarting my machine. Then I realized that the panels disappeared after gnome-screensaver had locked the screen for a while. I then had an idea to check the display properties and I noticed that my inactive LCD panel had been activated and thus my primary desktop had been moved to the LCD panel of the laptop (lid closed under my desk) and the panels were there. - Now, the easy work-around is to hit ctrl+F2 after the screensaver has + Now, the easy work-around is to hit alt+F2 after the screensaver has been unlocked, type gnome-display-properties and deactivate the LCD panel. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: gnome-screensaver 2.30.0-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.32-20.29-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-20-generic i686 Architecture: i386 Date: Tue Apr 13 09:34:35 2010 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None ProcEnviron: LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: gnome-screensaver WindowManager: metacity -- screensaver activates inactive display https://bugs.launchpad.net/bugs/562061 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 334377] Re: Lots of country names are missing, showing missing from libgweather in mobile broadband connection wizard.
thanks for your interest, but I already prepared a more detailed patch this morning which removes the broken code and uses g_dgettext. I will prepare a new package today or tomorrow. -- Lots of country names are missing, showing missing from libgweather in mobile broadband connection wizard. https://bugs.launchpad.net/bugs/334377 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 334377] Re: Lots of country names are missing, showing missing from libgweather in mobile broadband connection wizard.
Actually I don't have time to work on this right now, but it seems that I have to as it seems no one else is going to do it. I know this is really important and I really want to get this fixed. missing from libgweather is intended to make it clear for testers that libgweather is missing translations so that they can be added before a new release, but that's now irrelevant. I described the problem causing this bug on 2009-03-07. I'll do my best to get this fixed before FinalFreeze on 9.4. And yes, please, bump the Importance to High. I don't seem to have the permissions to do that myself. -- Lots of country names are missing, showing missing from libgweather in mobile broadband connection wizard. https://bugs.launchpad.net/bugs/334377 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 334377] Re: Lots of country names are missing, showing missing from libgweather in mobile broadband connection wizard.
yes, that's almost exactly all that's needed. There's another #ifndef in that file, too, and then there's a new dgettext () call needed where the country names are added to the visible list. -- Lots of country names are missing, showing missing from libgweather in mobile broadband connection wizard. https://bugs.launchpad.net/bugs/334377 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 334377] Re: Lots of country names are missing, showing missing from libgweather in mobile broadband connection wizard.
OK, I finally got my jaunty installation working and was able to investigate this. Fixing this needs a change in libmbca. It's not going to big, but I'm not yet sure how to fix this properly and I don't have time to work on this in at least couple of weeks.. The problem lays in http://svn.gnome.org/viewvc/libmbca/trunk/src/provider_thread.c?view=markup where the assistant tries to find country names based on country codes from libgweather database. The format changed with libgweather 2.23.6 and I hoped it would be stable from there on, but now it seems that the format is back what it used to be as the old code works on jaunty. After the name search is fixed there's a little translation related change required. Apparently debian has patched libgweather package to remove the translations from .xml file and to put them in gettext .mo's instead. For future releases libmbca could use resources from iso-codes package and wouldn't need libgweather anymore, but that change is too big for jaunty. ** Changed in: libmbca (Ubuntu) Status: New = In Progress -- Lots of country names are missing, showing missing from libgweather in mobile broadband connection wizard. https://bugs.launchpad.net/bugs/334377 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
