Added DEP-3 headers as recommend by Marc
** Patch added: "lp1582930_v3.debdiff"
https://bugs.launchpad.net/ubuntu/+source/psensor/+bug/1582930/+attachment/4698709/+files/lp1582930_v3.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Marc, thanks for the review and the comment. I am quite lost how to use
thse DEP-3 tags in practice, I will try to do it as soon as I understand
how to do it:(
** Changed in: psensor (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member
Second version of the patch (debdiff) adding a fix of a build failure
when a recent version of MHD is used.
** Patch added: "lp1582930_v2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/psensor/+bug/1582930/+attachment/4698703/+files/lp1582930_v2.debdiff
--
You received this bug
Attached the debdiff for Ubuntu Xenial which is fixing the issue
** Patch added: "lp1582930.debdiff"
https://bugs.launchpad.net/ubuntu/+source/psensor/+bug/1582930/+attachment/4678213/+files/lp1582930.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Hans-Gregor, you could use the PPA of psensor to get the fix:
sudo apt-add-repository ppa:jfi/ppa
sudo apt-get update
sudo apt-get install psensor
then restart psensor
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The release 1.1.5 of psensor is containing the fix.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1582930
Title:
psensor CPU usage jumps when graph window loses focus
To manage notifications about
Here is the fix:
http://wpitchoune.net/gitweb/?p=psensor.git;a=blobdiff;f=src/graph.c;h=60392cc14bbc748e6ce4b739c34ae61fda10494a;hp=792bb258d6679962ccf3904acadd5378030a9f18;hb=c9510a63205885497aa20ddf796cb90efb8c659b;hpb=555a434f8d3119f866eedbe05d9da225bb297b8f
--
You received this bug
You are right it is related to the theme.
The call of the GTK functions: gtk_widget_get_style_context,
gtk_style_context_get_background_color, tk_style_context_get_color are
emitting a draw signals to psensor when the widget does not have the
focus.
BTW, by caching the retrieval of fg/bg colors
Hans-Gregor, thanks for the report.
Currently I know that it is due to the gtk signal 'draw' which is sent by the
Gtk layer to psensor.
What I don't know is why the signal is sent. I wonder if it is not Unity. Did
you try another window manager?
--
You received this bug notification because
Thanks for the report, I am also reproducing it.
It is due to the fact that the signal 'draw' is called too often, so psensor is
refreshing
too often the curves leading to overusing the cpu.
Unfortunely, the signal 'draw' is not emitted by psensor itself so
currently, I don't have any fix.
--
Since the upgrade to nvidia 331.89, I no more reproduce the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1374965
Title:
nvidia-setting crashes on startup
To manage notifications about this
@Seth, I am the author of psensor.
I did the debdiff but unfortunely there is a specific ubuntu regression
The ubuntu packaging is linking /usr/share/psensor/www/jquery.js to
/usr/share/javascript/jquery/jquery.js which is rejected by the fix
(based on calling realpath C function)because it is
This error message simply indicate that the hddtemp daemon cannot be
accessed, usually because it is not running.
psensor does not use the hddtemp command but the hddtemp daemon so 'sudo
hddtemp' does not prove that the hddtemp daemon is working.
Please see information at
Public bug reported:
nvidia-settings
*** Error in `nvidia-settings': free(): invalid pointer: 0x7fd8a5b0f623 ***
Aborted
NVidia card: Asus GeForce GT 730 - 2 Go (DDR3)
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: nvidia-settings 331.20-0ubuntu8
ProcVersionSignature: Ubuntu
*** This bug is a duplicate of bug 1346299 ***
https://bugs.launchpad.net/bugs/1346299
** This bug has been marked a duplicate of bug 1346299
psensor does not start any more : Attempt to unlock mutex that was not locked
--
You received this bug notification because you are a member of
v1.1.1 is using Gsettings instead of GConf2 (1.0.x) and the settings is
not migrated so you have to redo the psensor setup. By default graph are
not draw, you just have to click on the 'graph' toggle at the right of
the sensor (main window).
v1.1.1 is not in the official repository and not
The glib package causing this issue has reached the utopic repository
which means that psensor is no more working on utopic now.
The very bad news is that I cannot branch the utopic version of psensor
to submit the trivial fix. It appears to be due to http://package-
As I am unable to checkout the utopic branch of psensor, submit the fix
as a debdiff.
** Patch added: Fix #1346299
https://bugs.launchpad.net/ubuntu/+source/psensor/+bug/1346299/+attachment/4184317/+files/lp1346299.patch
--
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 1346299 ***
https://bugs.launchpad.net/bugs/1346299
This bug has been fixed upstream since the release 1.0.3, you can use
the PPA: ppa:jfi/psensor-unstable to install it.
** This bug is no longer a duplicate of private bug 1357488
** This bug has been
The fix has been included in the v1.0.3 release. You can use the PPA:
ppa:jfi/psensor-unstable to use it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1346299
Title:
psensor does not start any
Reporter appears to use a glib version from a ppa and not from ubuntu
stock repositories.
The result of my investigation is that it is the consequence of a new check in
the glib since 2.41.
It is caused by the use of the deprecated function gdk_threads_init which is
only needed to workaround
a
I have another report from somebody else (directly send to my email), so
I turn it into 'confirmed'.
Are you using the trusty-proposed channel?
I am still interested by the gdb information if possible. Unlike previous
instructions it might be more useful to use the gdb
command 'thread apply all
@Jean, thanks for the useful information.
You forget the output of apt-cache policy psensor, I would like to
know which version of psensor is concerned to try to spot the cause of
your bug that I don't actually reproduce.
--
You received this bug notification because you are a member of Ubuntu
Are you using the stock release of psensor or a release from a PPA?
Could you please give the output of the 'apt-cache policy psensor'
command?
Do you reproduce systematically this issue?
Could you please:
- ensure that all instances of psensor are stopped: killall -9 psensor
- remove the log
** Changed in: psensor
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1258669
Title:
Threaded Programs Hang When Disposing Dialogs Created Via the Global
** Changed in: psensor
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/971098
Title:
Restarting unity shows two psensor icons in the unity bar
To manage
Just for the note: since the patch is not turning off the autostart but
removing the desktop file, it will require the user to understand that
they cannot simply use the 'startup application' of gnome and add
psensor. They will need to dig into $HOME/.config/autostart and tune the
desktop file in
** Branch linked: lp:~jfi/ubuntu/trusty/psensor/fix-LP1290072
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1290072
Title:
psensor icon in top bar too big
To manage notifications about this bug go
** Patch removed: lp1304108.patch
https://bugs.launchpad.net/ubuntu/+source/psensor/+bug/1304108/+attachment/4073396/+files/lp1304108.patch
** Patch added: lp1304108.debdiff
https://bugs.launchpad.net/ubuntu/+source/psensor/+bug/1304108/+attachment/4073864/+files/lp1304108.debdiff
--
** Branch linked: lp:~jfi/+junk/lp1304108
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1304108
Title:
FTBFS: cannot build psensor package on trusty due to deprecation of
GtkAction
To manage
** Branch unlinked: lp:~jfi/+junk/lp1304108
** Branch linked: lp:~jfi/ubuntu/trusty/psensor/fix-LP1304108
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1304108
Title:
FTBFS: cannot build psensor
It is fixed upstream in dev branch. You can give it a try by using the
package in the PPA: ppa:jfi/psensor-daily-trunk.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1290072
Title:
psensor icon in
** Patch added: gtk_warnings.patch
https://bugs.launchpad.net/ubuntu/+source/psensor/+bug/1304108/+attachment/4073376/+files/gtk_warnings.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
gtk_warnings.patch is fixing the build on trusty by allowing deprecated
GTK functions.
I have do a real fix upstream but it has far more impact (many code and
glade files) and risk than this patch. I believe that it is more safe to
apply the attached patch than the 'real fix'.
As I have
Public bug reported:
Since the deprecation of GtkAction it is no more possible to rebuild
psensor package on Trusty.
See: https://launchpadlibrarian.net/171034253/buildlog_ubuntu-trusty-
ppc64el.psensor_0.8.0.3-1ubuntu1_FAILEDTOBUILD.txt.gz
** Affects: psensor (Ubuntu)
Importance:
** Patch removed: gtk_warnings.patch
https://bugs.launchpad.net/ubuntu/+source/psensor/+bug/1304108/+attachment/4073376/+files/gtk_warnings.patch
** Patch added: lp1304108.patch
https://bugs.launchpad.net/ubuntu/+source/psensor/+bug/1304108/+attachment/4073396/+files/lp1304108.patch
**
@Laryllan ok, so you did not change some DE configuration to use the
traybar support instead of appindicator support.
BTW, I have quickly installed trusty + psensor and can confirm the bad
scaling of the icon. Note that it cannot be reproduced with Saucy.
Unfortunely, I have no idea of what is
Well, I understood the issue, vanilla Unity icons are including a
padding... I have to do the same to have a consistent size.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1290072
Title:
psensor
I don't reproduce with saucy.
The icon scaling is strange it sounds like it is the traybar and not the
appindicator area.
Could you please left click on the icon and let me know if there is a
menu? If not it is the traybar icon.
** Changed in: psensor (Ubuntu)
Status: Confirmed =
Since very recent updates in the past 2 days of saucy, I am reproducing
the issue with all releases of psensor since 0.6 which means that it is
due to a change in underlying libraries (gtk, DE, etc) and not psensor.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
@David don't waste your time, I am now reproducing it, I do not need
more help from you. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1267565
Title:
psensor hangs when closing preferences
Can be fixed by adding gdk_thread_enter/leave around gtk_dialog_run.
Guess the calls are missing in the Unity specific handling of the menus.
BTW, addind these calls may lead to freeze for other DEs... Require more
investigation and undestanding and may be a fix on Unity instead of
Psensor.
--
Obviously, it is related to the global Unity menu so to workaround the
issue, disable it for psensor by launching it using:
env UBUNTU_MENU_PROXY= psensor
@David could you please give a try to this workaround so I will be 100%
sure that your report is not about another issue?
--
You received
*** This bug is a duplicate of bug 1258669 ***
https://bugs.launchpad.net/bugs/1258669
@Jorg configuration is using dconf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1268575
Title:
by saving
*** This bug is a duplicate of bug 1258669 ***
https://bugs.launchpad.net/bugs/1258669
** This bug has been marked a duplicate of bug 1258669
Threaded Programs Hang When Disposing Dialogs Created Via the Global Menu
--
You received this bug notification because you are a member of Ubuntu
*** This bug is a duplicate of bug 1258669 ***
https://bugs.launchpad.net/bugs/1258669
Should be due to: https://bugs.launchpad.net/unity-gtk-
module/+bug/1258669
** This bug has been marked a duplicate of bug 1258669
Threaded Programs Hang When Disposing Dialogs Created Via the Global
*** This bug is a duplicate of bug 1258669 ***
https://bugs.launchpad.net/bugs/1258669
env UBUNTU_MENUPROXY= psensor
UBUNTU_MENUPROXY (and not UBUNTU_MENU_PROXY)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Are you sure that the hddtemp daemon is running?
Since few release hddtemp packaging is turning off the daemon.
You need to install the hddtemp package, edit etc/default/hddtemp and replace
RUN_DAEMON=false by RUN_DAEMON=true.
** Changed in: psensor (Ubuntu)
Status: Confirmed =
*** This bug is a duplicate of bug 1267565 ***
https://bugs.launchpad.net/bugs/1267565
@Jorg could you please try without the sensor logging:
- Menu preferences and turn off enable sensors logging
- stop all psensor instances: killall -9 psensor
- restart psensor
- retry your scenario.
Did you enable the logging of sensors (in the preferences the option
Enable sensors logging)?
Do you reproduce each the issue? (I did not reproduce it but I can only
use Trusty in a VM).
Could you please describe exactly the steps to reproduce? How are you
changing the sensor color (click
Before I install trusty to check, could you please:
- stop all instances of psensor: killall -9 psensor
- remove the log: rm $HOME/.psensor/log
- restart psensor with debug logging: psensor -d3
- send me or attach $HOME/.psensor/log
--
You received this bug notification because you are a
Forget a step before sending the log:
-reproduce the issue
:)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1267565
Title:
psensor hangs when closing preferences
To manage notifications about
@Simon, yes, I have only patched the glade 3.14.2. I am going to check
whether the same fix can be applied to the 3.8.0 package (in fact that's
glade-gtk2) too and upload to my ppa if it works.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Unfortunely, the fix is not working for glade-gtk2. Guess it depends on another
changes that is in glade 3.14.2 but not glade 3.8.0.
You should probably open a separate bug report.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Sounds like the fix is:
https://git.gnome.org/browse/glade/patch/?id=d2c8e008e1b81d501b30c070d492959da6922992
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1242865
Title:
Glade can't work with
debdiff fix for LP#1242865
Only contains changes for the fix, from glade author:
https://git.gnome.org/browse/glade/patch/?id=d2c8e008e1b81d501b30c070d492959da6922992
** Patch added: lp1242865.debdiff
I have uploaded .deb with the fix to a PPA: ppa:jfi/test
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1242865
Title:
Glade can't work with dialog windows
To manage notifications about this bug go
Sounds like there is already a registered report on the glade bugs database:
https://bugzilla.gnome.org/show_bug.cgi?id=705745
** Bug watch added: GNOME Bug Tracker #705745
https://bugzilla.gnome.org/show_bug.cgi?id=705745
--
You received this bug notification because you are a member of
- Core dump when using any .glade file containing a dialog box.
- Impossible to design a dialog box (more exactly to add something in it)
- Even the glade example at
https://developer.gnome.org/gtk3/unstable/GtkDialog.html is producing a core
dump when loading it with glade
Here is the stack:
I tried 2 others DEs (gnome and enlightment), same issue for glade.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1242865
Title:
Glade can't work with dialog windows
To manage notifications about
rebuilt the debian unstable package on ubuntu saucy, same issue which is
not surprising as mentionned by #11 the differences between the 2
packages do not sound related to the bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Guess there is some relation with #1242865
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1222753
Title:
Glade can't create a dialog
To manage notifications about this bug go to:
Only primary button and double click settings are available, missing
'pointer speed', 'drag and drop' and 'double click timeout' settings.
Microsoft Comfort Mouse 6000 is a wired mouse.
xinput --list
⎡ Virtual core pointer id=2[master pointer (3)]
⎜ ↳ Virtual core
Public bug reported:
Due to a Saucy GTK update, psensor cannot be build.
The error is due to the deprecation of the GTK Color Selection widget,
and the Psensor build fails on deprecation warnings.
** Affects: psensor (Ubuntu)
Importance: Undecided
Status: New
--
You received
Debdiff fixing this bug by allowing usage of deprecated gtk widgets.
This issue is fixed upstream in the trunk repository by replacing the
deprecated GtkColorSelectionDialog by GtkColorChooserDialog. It will be
available in the future 0.8.0.3 release of Psensor.
Additionnaly, this patch also
Dear sponsor,
I am going to release a new version of Psensor including the real fix and push
its debian package. Unfortunely, as I do not have a debian sponsor it may take
a while.
As the above patch is a one line change, I guess it is better to apply it than
wait the debian package to be
I do not reproduce with raring (nor precise).
To decide whether psensor needs to hide the main window it requires that
the appindicator service is started after a given amount of time. If the
session is very long to open, it causes trouble. The duration has been
extended in a 0.7.0.4.
--
You
Hello,
Even if it appears simple, It depends on the DE, multiple bugs have been
fixed for various environment.
Could you please install psensor from the PPA ppa:jfi/psensor-daily-
trunk and let me know if it works fine.
If it is not the case, I need more information:
- Which DE are using?
-
You mean that you reproduce the issue with the psensor release from the
daily ppa?
Could you please edit /etc/xdg/autostart/psensor.desktop
and set the value of X-GNOME-Autostart-Delay to a number of seconds greater
that the time needed to fully open a session on your computer?
If it does not
On the technical side, the issue is due to the fact that the
appindicator service is not started *BEFORE* the autostarted
applications are started.
Psensor desktop file set the autostart delay to 30s and psensor waits 2s
(30s since 0.7.0.4 ) after its launch to check that the appindicator is
not
Reply to #4:
Waiting the appindicator launch is not the problem, the problem is that it is
not possible to know whether or not the appindicator
is going to be started.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: psensor
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1029065
Title:
usr/share/icons/hicolor/48x48/apps/psensor_hot.png has wrong size and
wrong
Hello Marek,
You expose different problems from this report:
1 - autostart is not correctly working with KDE which surprises me a lot and is
probably not a Psensor issue
2 - psensor can run twice: this is not really a bug, but a missing feature.
For 1) I would recommend to open a separate bug,
gedit, evince, update-manager, and psensor is displaying this warning
(I did not test evolution which is not installed on my computer).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1061554
Title:
** Changed in: psensor
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1021900
Title:
psensor should show a proper Celsius degree symbol
To manage
The fix is included in Psensor since v0.7.0.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/971098
Title:
Restarting unity shows two psensor icons in the unity bar
To manage notifications about
For the log, a user has reported that this issue can be reproduced on
XUbuntu 12.04 with the stock version of psensor (0.6.2.16) and that it
is fixed with the 0.7.0.3 release.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Branch linked: lp:~jfi/ubuntu/quantal/psensor/new-upstream-0-6-2-19
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1029065
Title:
usr/share/icons/hicolor/48x48/apps/psensor_hot.png has wrong size
** Branch linked: lp:~jfi/psensor/0.6.2.19
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1029065
Title:
usr/share/icons/hicolor/48x48/apps/psensor_hot.png has wrong size and
wrong look
To manage
On 11/15/2010 06:36 PM, Achraf Fouwad wrote:
jacques il ne reste attaché dans le screen que tant que la session dans
laquelle il était lancé tourne !
justement non:)
brievement pour l'utiliser:
1 - tu tapes screen
2 - tu lances ton programme shell
3 - control-a d (control et 'a' appuye en
On 11/14/2010 12:06 PM, Steve Nadeau wrote:
à moins qu'il y ait un moyen de récupérer le terminal déjà ouvert, mais
comme il s'agit d'une exécution en cours il ne faut pas confondre avec
de nouvelles exécutions de sqlplus.
byobu/screen permet de se 'reconnecter' a un shell.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/14/2010 12:14 PM, Steve Nadeau wrote:
mais comme mentionné, le terminal est présentement en exécution et
il s'agit d'un terminal normal, pas lancé avec screen ou autre...
je veux tout simplement lui lancer la commande commit à distance...
On 05/04/2010 11:42 AM, Wad G wrote:
megasas: Failed to copy out to user sense data
https://bugzilla.kernel.org/show_bug.cgi?id=15001 ?
--
ubuntu-fr mailing list
ubuntu-fr@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-fr
83 matches
Mail list logo
