Bug 116120 - smssend: use provider-files in ~/.smssend
Summary: smssend: use provider-files in ~/.smssend
Status: RESOLVED WORKSFORME
Alias: None
Product: kopete
Classification: Applications
Component: SMS Plugin (show other bugs)
Version: 0.40.0
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-11-11 11:15 UTC by Niko Sams
Modified: 2023-01-18 05:11 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Niko Sams 2005-11-11 11:15:19 UTC
Version:           0.10.3 (using KDE KDE 3.4.2)
Installed from:    Debian testing/unstable Packages
OS:                Linux

from man smssend:
The needed provider files are installed by default to /usr/share/smssend.  When invoking smssend with a  provider,  the  program  first looks for the corresponding file in the current directory, then in ~/.smssend/, and finally in the shared directory.

Steps to reproduce this:
- copy a provider file from /usr/share/smssend/ to ~/.smssend/
- modify the provider file (change the parameters)
- open the smssend-configuration-dialog in kopete
current behavior:
notice the old parameters are shown there!

expected result:
- the parameters from ~/.smssend/ should be used
Comment 1 Andrew Crouthamel 2018-11-05 03:17:37 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 2 Andrew Crouthamel 2018-11-17 05:04:39 UTC
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Justin Zobel 2022-12-19 00:13:27 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 4 Bug Janitor Service 2023-01-03 05:26:22 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Bug Janitor Service 2023-01-18 05:11:34 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!