On 12.04 open dconf-editor and go to org.gnome.gnome-system-log,
logfiles are defined here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/318689
Title:
gnome-system-log attempts to open bogus/inexis
I upgraded from Ubuntu 9.04 to Ubuntu 10.04 LTS - the Lucid Lynx and I
had the same problem.
gnome-system-log - Version 2.30.0
This is also work for my system:
Running 'gconftool-2 --recursive-unset /apps/gnome-system-log' fixed the issue.
--
You received this bug notification because you are
I had this message about an old log file that no longer existed.
Running 'gconftool-2 --recursive-unset /apps/gnome-system-log' fixed the
issue.
gnome-system-log - Version 2.32.0 on Natty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
** Changed in: gnome-utils
Importance: Unknown => Medium
--
gnome-system-log attempts to open bogus/inexistent logfiles
https://bugs.launchpad.net/bugs/318689
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing lis
** Tags added: patch
--
gnome-system-log attempts to open bogus/inexistent logfiles
https://bugs.launchpad.net/bugs/318689
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://
> ok, could you
> - run "gnome-system-log --version"
> - run "gconftool-2 --recursive-unset /apps/gnome-system-log" and try to start
> gnome-system-log and see if there is an error
Thanks this solve my issue on Karmic Koala
--
gnome-system-log attempts to open bogus/inexistent logfiles
https:/
** Branch linked: lp:ubuntu/gnome-utils
--
gnome-system-log attempts to open bogus/inexistent logfiles
https://bugs.launchpad.net/bugs/318689
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.
Just noticed this problem after a "rm /var/log/*.gz" to clean up my log
directory...
I guess it's not going to be fixed until karmic?
** Attachment added: "Log-Deleted-Files.png"
http://launchpadlibrarian.net/28646216/Log-Deleted-Files.png
--
gnome-system-log attempts to open bogus/inexisten
[...]
> - run "gnome-system-log --version"
gnome-system-log - Version 2.25.92
...
(btw. was upgraded after my last bugreport update)
> - run "gconftool-2 --recursive-unset /apps/gnome-system-log" and try to
> start gnome-system-log and see if there is an error -
No error at all.
> log as a new
ok, could you
- run "gnome-system-log --version"
- run "gconftool-2 --recursive-unset /apps/gnome-system-log" and try to start
gnome-system-log and see if there is an error
- log as a new user or use a guest session and start gnome-system-log and see
if you get an error
and then update the bug
Am Fr, 6. März 2009 09:49:46 schrieb Sebastien Bacher:
> > - still uses hardcoded obsolete values of bogus logfiles
>
> no it doesn't
Shure?
Before sending bug report I did the following:
- run gnome-system-log
it shows the known list of nonexistant logfiles
- run gconf-editor and deleted '/a
> - still uses hardcoded obsolete values of bogus logfiles
no it doesn't
--
gnome-system-log attempts to open bogus/inexistent logfiles
https://bugs.launchpad.net/bugs/318689
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bu
gnome-utils (2.25.92-0ubuntu1)
- still uses hardcoded obsolete values of bogus logfiles
- there is no value set for loglist in gconf-editor under
/apps/gnome-system-log as mentioned by Hernando Torque
--
gnome-system-log attempts to open bogus/inexistent logfiles
https://bugs.launchpad.net/bugs
the janitor has nothing to do with that, the issue reported there has
been fixed, the logs file is not static but built on first start and
users who didn't run previous jaunty version will have no such issue,
I've reopen the bug to address the issue with the gconf key or log
changes though
the nom
As I said it's only fixed for the first startup. If you've already
started the log viewer (with an earlier version) you need to unset the
loglist in gconf-editor under /apps/gnome-system-log to realize the
difference.
Making this list editable within the application would probably fix the
remainin
Sebastien I'm confused - the bug is in a triaged status yet the janitor
thinks this is fixed? It is *not* fixed, the behaviour is still occuring
for me on:
null...@ppp:~$ sudo apt-cache policy gnome-utils
gnome-utils:
Installed: 2.25.92-0ubuntu1
Candidate: 2.25.92-0ubuntu1
Version table:
**
** Changed in: gnome-utils (Ubuntu)
Status: Fix Released => Triaged
--
gnome-system-log attempts to open bogus/inexistent logfiles
https://bugs.launchpad.net/bugs/318689
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-b
That only fixes the warning for the first startup. Non existant files
still cannot be removed via the application (you either have to remove
them from the gconf list or recreate them on disk and then close them in
the log viewer).
--
gnome-system-log attempts to open bogus/inexistent logfiles
htt
This bug was fixed in the package gnome-utils - 2.25.92-0ubuntu1
---
gnome-utils (2.25.92-0ubuntu1) jaunty; urgency=low
* New upstream version:
Baobab
- Use g_return_val_if_fail instead of g_return_if_fail.
Dictionary
- Replace deprecated gtk_entry_set_editable.
As for the user added files that no longer exist: I'd rather leave them
in the log list (grayed out to visualize their absence) so the user can
close them (which will permanently remove them from gconf) than remove
them directly, but I don't know how to do that (lack of GTK programming
experience).
Really strange. I always thought it's sufficient to purge a package to
get rid of all gconf data but I needed to restart GDM for a clean gconf.
Ok, I tested the trivial fix (as already said I just check if
default_logfiles[i] exist with fopen) and it seems to work.
Only Xorg.0.log gets added, the
Hernando, you have to go into the directory ~/.gconf/apps/ and remove
the directory gnome-system-log.
--
gnome-system-log attempts to open bogus/inexistent logfiles
https://bugs.launchpad.net/bugs/318689
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
How can I get rid of gnome-system-log in gconf? Uninstalling (and
purging) gnome-utils didn't fix it.
I think you just need to check the existence of default_logfiles[i] in
logview_prefs_fill_defaults (I did it with fopen - maybe overkill?) but
as long as I have the gconf entry present it's not cr
On Fri, 2009-02-20 at 10:13 +, Sebastien Bacher wrote:
> thank for your work but I'm not convinced by this approch, it should
> just lists all the available logs listed and not display an error dialog
> which has no use
Hi Sebastien.
I wasn't attempting to fix the fundamental issue, just to m
thank for your work but I'm not convinced by this approch, it should
just lists all the available logs listed and not display an error dialog
which has no use
--
gnome-system-log attempts to open bogus/inexistent logfiles
https://bugs.launchpad.net/bugs/318689
You received this bug notification b
The patch above doesn't deal with the issue that gnome-log-viewer
seemingly doesn't provide for the user deleting a log-file from the
monitored list if that file doesn't exist on-disk.
--
gnome-system-log attempts to open bogus/inexistent logfiles
https://bugs.launchpad.net/bugs/318689
You receiv
Thanks for pointing that out Steve. I moved an existing /home/ mount
into the Jaunty environment. Now you've jogged my memory I think I do
recall that with the default Jaunty user profile I saw a bunch of log-
file warnings too. Now I only see one for /var/log/acpid.
The reason for it is that on p
In the upstream gnome bug report, TJ commented:
> The cause seems to be a user profile that has been upgraded from an older
> distro release, where the contents of /var/log/ haven't been inherited. It can
> also happen where multiple release installations share a common /home/$USER/.
However, I s
Same problem here on Kernel 2.6.28-6 64 bit. Not seen in Alpha3 but seen
in Alpha4.
--
gnome-system-log attempts to open bogus/inexistent logfiles
https://bugs.launchpad.net/bugs/318689
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Attachment added: "Pic of error message"
http://launchpadlibrarian.net/22413610/Screenshot-lpr.log%20-%20System%20Log%20Viewer.png
--
gnome-system-log attempts to open bogus/inexistent logfiles
https://bugs.launchpad.net/bugs/318689
You received this bug notification because you are a mem
** Changed in: gnome-utils
Status: Unknown => New
--
gnome-system-log attempts to open bogus/inexistent logfiles
https://bugs.launchpad.net/bugs/318689
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
u
Thank you for your bug report, that's a known issue you can read about
it on http://bugzilla.gnome.org/show_bug.cgi?id=567169
** Changed in: gnome-utils (Ubuntu)
Importance: Undecided => Low
Assignee: (unassigned) => Ubuntu Desktop Bugs (desktop-bugs)
Status: New => Triaged
** Also
32 matches
Mail list logo
