I just started seeing a similar problem, but my output of "$ kcmshell
displayconfig" is a bit different:
$ kcmshell displayconfig
Pythonize constructor -- pid = 11128
Python interpreter initialized!
Pythonize constructor -- pid = 11128
open /dev/mem: Permission denied
VESA BIOS Extensions not de
This bug has reappeared after updating Edgy on Sept. 30, 2006. The beta
was fine, but after updating, these modules no longer work, either from
kde-systemsettings or from kcontrol. I haven't tried "kcmshell
displayconfig" from the command line, but will do so tonight when I am
at home.
--
systems
I could confirm this bug before. However, the modules all seem to be
loading fine for me now...
** Bug 63546 has been marked a duplicate of this bug
--
systemsettings doesn't load Display, Disk and Filesystems control module
https://launchpad.net/bugs/38692
--
ubuntu-bugs mailing list
ubuntu-
Confirming due to a number of duplicates as well as I had this issue
previously as well and thought it had been fixed.
** Changed in: kde-systemsettings (Ubuntu)
Importance: Medium => High
Status: Needs Info => Confirmed
--
systemsettings doesn't load Display, Disk and Filesystems cont
Can anyone else confirm the fix?
--
systemsettings doesn't load Display, Disk and Filesystems control module
https://launchpad.net/bugs/38692
--
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
With Edgy/Kubuntu the original load did not have this problem.
It appeared on all 4 of my systems after an update in the middle of January.
The problem appeared "universal" so I did not attempt reporting a problem,
assuming a fix would be forthcoming.
I update my systems at least once a week and
** Changed in: kde-guidance (Ubuntu)
Sourcepackagename: kde-systemsettings => kde-guidance
** Changed in: kde-guidance (Ubuntu)
Assignee: Kubuntu Bugs (kubuntu-bugs) => (unassigned)
--
systemsettings doesn't load Display, Disk and Filesystems control module
https://bugs.launchpad.net/bugs/3
I have had this bug in Feisty and still have it in Gutsy.
OUTPUT--
[EMAIL PROTECTED]:~$ kcmshell displayconfig
Pythonize constructor -- pid = 5315
Python interpreter initialized!
Pythonize constructor -- pid = 5315
open /dev/mem: Permission denied
VESA BIOS Extensions n
Has anyone observed the problem on Hardy?
--
systemsettings doesn't load Display, Disk and Filesystems control module
https://bugs.launchpad.net/bugs/38692
You received this bug notification because you are a member of Kubuntu
Team, which is a direct subscriber.
--
kubuntu-bugs mailing list
[EM
This bug happened to me soon after installing Kubuntu 7.10 on what was
previously a Windows only box. System is dual monitor. The module
stopped working a few steps after after I had successfully enabled the
second monitor. The monitor first came up as a generic with only 640x480
available, so I re
Yes, I'm experiencing this in hardy
I tried displayconfig and kcmshell displayconfig but this didn't work
(using radeonhd, if it matters)
--
systemsettings doesn't load Display, Disk and Filesystems control module
https://bugs.launchpad.net/bugs/38692
You received this bug notification because y
I still have the same problem.
Is there any workaround here?
There is settings window snapshot in attachment.
$ sudo kcmshell displayconfig
Password:
X Error: BadDevice, invalid or uninitialized input device 169
Major opcode: 145
Minor opcode: 3
Resource id: 0x0
Failed to open device
X Er
@prokher: Your problem is a different issue. Use "kdesu kcmshell
displayconfig" or "kdesu displayconfig", either should work.
--
systemsettings doesn't load Display, Disk and Filesystems control module
https://bugs.launchpad.net/bugs/38692
You received this bug notification because you are a memb
$ kdesu displayconfig
X Error: BadDevice, invalid or uninitialized input device 169
Major opcode: 145
Minor opcode: 3
Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 169
Major opcode: 145
Minor opcode: 3
Resource id: 0x0
Failed to o
With Hardy Release: happens for "Disk and Filesystems" and "User
management" modules if they are opened after opening "Printers" module
Steps to reproduce:
1) open "System Settings" or run systemsettings in konsole
2) open "Printers" and press the back button to go back
3) open "Disk and Filesyste
confirming
--
systemsettings doesn't load Display, Disk and Filesystems control module
https://bugs.launchpad.net/bugs/38692
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https:/
Has happened to me with Disk and Filesystems on Hardy RC. I had rebooted after
doing the update from Gutsy to Hardy RC and was opening all the System settings
one by one to look at any new features and the Disk and Filesystems module
failed to load. However after i closed and reopened System set
Has happened to me with Disk and Filesystems on Hardy RC. I had rebooted after
doing the update from Gutsy to Hardy RC and was opening all the System settings
one by one to look at any new features and the Disk and Filesystems module
failed to load. However after i closed and reopened System set
With Hardy Release: happens for "Disk and Filesystems" and "User
management" modules if they are opened after opening "Printers" module
Steps to reproduce:
1) open "System Settings" or run systemsettings in konsole
2) open "Printers" and press the back button to go back
3) open "Disk and Filesyste
confirming
--
systemsettings doesn't load Display, Disk and Filesystems control module
https://bugs.launchpad.net/bugs/38692
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https:/
I have had this bug in Feisty and still have it in Gutsy.
OUTPUT--
[EMAIL PROTECTED]:~$ kcmshell displayconfig
Pythonize constructor -- pid = 5315
Python interpreter initialized!
Pythonize constructor -- pid = 5315
open /dev/mem: Permission denied
VESA BIOS Extensions n
Has anyone observed the problem on Hardy?
--
systemsettings doesn't load Display, Disk and Filesystems control module
https://bugs.launchpad.net/bugs/38692
You received this bug notification because you are a member of Kubuntu
Team, which is a direct subscriber.
--
kubuntu-bugs mailing list
[EM
Yes, I'm experiencing this in hardy
I tried displayconfig and kcmshell displayconfig but this didn't work
(using radeonhd, if it matters)
--
systemsettings doesn't load Display, Disk and Filesystems control module
https://bugs.launchpad.net/bugs/38692
You received this bug notification because y
This bug happened to me soon after installing Kubuntu 7.10 on what was
previously a Windows only box. System is dual monitor. The module
stopped working a few steps after after I had successfully enabled the
second monitor. The monitor first came up as a generic with only 640x480
available, so I re
I just started seeing a similar problem, but my output of "$ kcmshell
displayconfig" is a bit different:
$ kcmshell displayconfig
Pythonize constructor -- pid = 11128
Python interpreter initialized!
Pythonize constructor -- pid = 11128
open /dev/mem: Permission denied
VESA BIOS Extensions not de
This bug has reappeared after updating Edgy on Sept. 30, 2006. The beta
was fine, but after updating, these modules no longer work, either from
kde-systemsettings or from kcontrol. I haven't tried "kcmshell
displayconfig" from the command line, but will do so tonight when I am
at home.
--
systems
I could confirm this bug before. However, the modules all seem to be
loading fine for me now...
** Bug 63546 has been marked a duplicate of this bug
--
systemsettings doesn't load Display, Disk and Filesystems control module
https://launchpad.net/bugs/38692
--
ubuntu-bugs mailing list
ubuntu-
Confirming due to a number of duplicates as well as I had this issue
previously as well and thought it had been fixed.
** Changed in: kde-systemsettings (Ubuntu)
Importance: Medium => High
Status: Needs Info => Confirmed
--
systemsettings doesn't load Display, Disk and Filesystems cont
Can anyone else confirm the fix?
--
systemsettings doesn't load Display, Disk and Filesystems control module
https://launchpad.net/bugs/38692
--
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
With Edgy/Kubuntu the original load did not have this problem.
It appeared on all 4 of my systems after an update in the middle of January.
The problem appeared "universal" so I did not attempt reporting a problem,
assuming a fix would be forthcoming.
I update my systems at least once a week and
I still have the same problem.
Is there any workaround here?
There is settings window snapshot in attachment.
$ sudo kcmshell displayconfig
Password:
X Error: BadDevice, invalid or uninitialized input device 169
Major opcode: 145
Minor opcode: 3
Resource id: 0x0
Failed to open device
X Er
@prokher: Your problem is a different issue. Use "kdesu kcmshell
displayconfig" or "kdesu displayconfig", either should work.
--
systemsettings doesn't load Display, Disk and Filesystems control module
https://bugs.launchpad.net/bugs/38692
You received this bug notification because you are a memb
$ kdesu displayconfig
X Error: BadDevice, invalid or uninitialized input device 169
Major opcode: 145
Minor opcode: 3
Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 169
Major opcode: 145
Minor opcode: 3
Resource id: 0x0
Failed to o
** Changed in: kde-guidance (Ubuntu)
Sourcepackagename: kde-systemsettings => kde-guidance
** Changed in: kde-guidance (Ubuntu)
Assignee: Kubuntu Bugs (kubuntu-bugs) => (unassigned)
--
systemsettings doesn't load Display, Disk and Filesystems control module
https://bugs.launchpad.net/bugs/3
I just started seeing a similar problem, but my output of "$ kcmshell
displayconfig" is a bit different:
$ kcmshell displayconfig
Pythonize constructor -- pid = 11128
Python interpreter initialized!
Pythonize constructor -- pid = 11128
open /dev/mem: Permission denied
VESA BIOS Extensions not de
This bug has reappeared after updating Edgy on Sept. 30, 2006. The beta
was fine, but after updating, these modules no longer work, either from
kde-systemsettings or from kcontrol. I haven't tried "kcmshell
displayconfig" from the command line, but will do so tonight when I am
at home.
--
systems
I could confirm this bug before. However, the modules all seem to be
loading fine for me now...
** Bug 63546 has been marked a duplicate of this bug
--
systemsettings doesn't load Display, Disk and Filesystems control module
https://launchpad.net/bugs/38692
--
ubuntu-bugs mailing list
ubuntu-
** Changed in: kde-guidance (Ubuntu)
Sourcepackagename: kde-systemsettings => kde-guidance
** Changed in: kde-guidance (Ubuntu)
Assignee: Kubuntu Bugs (kubuntu-bugs) => (unassigned)
--
systemsettings doesn't load Display, Disk and Filesystems control module
https://bugs.launchpad.net/bugs/3
Has anyone observed the problem on Hardy?
--
systemsettings doesn't load Display, Disk and Filesystems control module
https://bugs.launchpad.net/bugs/38692
You received this bug notification because you are a member of Kubuntu
Team, which is a direct subscriber.
--
kubuntu-bugs mailing list
[EM
This bug happened to me soon after installing Kubuntu 7.10 on what was
previously a Windows only box. System is dual monitor. The module
stopped working a few steps after after I had successfully enabled the
second monitor. The monitor first came up as a generic with only 640x480
available, so I re
I still have the same problem.
Is there any workaround here?
There is settings window snapshot in attachment.
$ sudo kcmshell displayconfig
Password:
X Error: BadDevice, invalid or uninitialized input device 169
Major opcode: 145
Minor opcode: 3
Resource id: 0x0
Failed to open device
X Er
@prokher: Your problem is a different issue. Use "kdesu kcmshell
displayconfig" or "kdesu displayconfig", either should work.
--
systemsettings doesn't load Display, Disk and Filesystems control module
https://bugs.launchpad.net/bugs/38692
You received this bug notification because you are a memb
$ kdesu displayconfig
X Error: BadDevice, invalid or uninitialized input device 169
Major opcode: 145
Minor opcode: 3
Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 169
Major opcode: 145
Minor opcode: 3
Resource id: 0x0
Failed to o
I have had this bug in Feisty and still have it in Gutsy.
OUTPUT--
[EMAIL PROTECTED]:~$ kcmshell displayconfig
Pythonize constructor -- pid = 5315
Python interpreter initialized!
Pythonize constructor -- pid = 5315
open /dev/mem: Permission denied
VESA BIOS Extensions n
Yes, I'm experiencing this in hardy
I tried displayconfig and kcmshell displayconfig but this didn't work
(using radeonhd, if it matters)
--
systemsettings doesn't load Display, Disk and Filesystems control module
https://bugs.launchpad.net/bugs/38692
You received this bug notification because y
Confirming due to a number of duplicates as well as I had this issue
previously as well and thought it had been fixed.
** Changed in: kde-systemsettings (Ubuntu)
Importance: Medium => High
Status: Needs Info => Confirmed
--
systemsettings doesn't load Display, Disk and Filesystems cont
Can anyone else confirm the fix?
--
systemsettings doesn't load Display, Disk and Filesystems control module
https://launchpad.net/bugs/38692
--
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
With Edgy/Kubuntu the original load did not have this problem.
It appeared on all 4 of my systems after an update in the middle of January.
The problem appeared "universal" so I did not attempt reporting a problem,
assuming a fix would be forthcoming.
I update my systems at least once a week and
With Hardy Release: happens for "Disk and Filesystems" and "User
management" modules if they are opened after opening "Printers" module
Steps to reproduce:
1) open "System Settings" or run systemsettings in konsole
2) open "Printers" and press the back button to go back
3) open "Disk and Filesyste
confirming
--
systemsettings doesn't load Display, Disk and Filesystems control module
https://bugs.launchpad.net/bugs/38692
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https:/
Has happened to me with Disk and Filesystems on Hardy RC. I had rebooted after
doing the update from Gutsy to Hardy RC and was opening all the System settings
one by one to look at any new features and the Disk and Filesystems module
failed to load. However after i closed and reopened System set
Confirming due to a number of duplicates as well as I had this issue
previously as well and thought it had been fixed.
** Changed in: kde-systemsettings (Ubuntu)
Importance: Medium => High
Status: Needs Info => Confirmed
--
systemsettings doesn't load Display, Disk and Filesystems cont
Can anyone else confirm the fix?
--
systemsettings doesn't load Display, Disk and Filesystems control module
https://launchpad.net/bugs/38692
--
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
With Edgy/Kubuntu the original load did not have this problem.
It appeared on all 4 of my systems after an update in the middle of January.
The problem appeared "universal" so I did not attempt reporting a problem,
assuming a fix would be forthcoming.
I update my systems at least once a week and
Has anyone observed the problem on Hardy?
--
systemsettings doesn't load Display, Disk and Filesystems control module
https://bugs.launchpad.net/bugs/38692
You received this bug notification because you are a member of Kubuntu
Team, which is a direct subscriber.
--
kubuntu-bugs mailing list
[EM
This bug happened to me soon after installing Kubuntu 7.10 on what was
previously a Windows only box. System is dual monitor. The module
stopped working a few steps after after I had successfully enabled the
second monitor. The monitor first came up as a generic with only 640x480
available, so I re
Yes, I'm experiencing this in hardy
I tried displayconfig and kcmshell displayconfig but this didn't work
(using radeonhd, if it matters)
--
systemsettings doesn't load Display, Disk and Filesystems control module
https://bugs.launchpad.net/bugs/38692
You received this bug notification because y
With Hardy Release: happens for "Disk and Filesystems" and "User
management" modules if they are opened after opening "Printers" module
Steps to reproduce:
1) open "System Settings" or run systemsettings in konsole
2) open "Printers" and press the back button to go back
3) open "Disk and Filesyste
confirming
--
systemsettings doesn't load Display, Disk and Filesystems control module
https://bugs.launchpad.net/bugs/38692
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https:/
Has happened to me with Disk and Filesystems on Hardy RC. I had rebooted after
doing the update from Gutsy to Hardy RC and was opening all the System settings
one by one to look at any new features and the Disk and Filesystems module
failed to load. However after i closed and reopened System set
I have had this bug in Feisty and still have it in Gutsy.
OUTPUT--
[EMAIL PROTECTED]:~$ kcmshell displayconfig
Pythonize constructor -- pid = 5315
Python interpreter initialized!
Pythonize constructor -- pid = 5315
open /dev/mem: Permission denied
VESA BIOS Extensions n
I just started seeing a similar problem, but my output of "$ kcmshell
displayconfig" is a bit different:
$ kcmshell displayconfig
Pythonize constructor -- pid = 11128
Python interpreter initialized!
Pythonize constructor -- pid = 11128
open /dev/mem: Permission denied
VESA BIOS Extensions not de
This bug has reappeared after updating Edgy on Sept. 30, 2006. The beta
was fine, but after updating, these modules no longer work, either from
kde-systemsettings or from kcontrol. I haven't tried "kcmshell
displayconfig" from the command line, but will do so tonight when I am
at home.
--
systems
I could confirm this bug before. However, the modules all seem to be
loading fine for me now...
** Bug 63546 has been marked a duplicate of this bug
--
systemsettings doesn't load Display, Disk and Filesystems control module
https://launchpad.net/bugs/38692
--
ubuntu-bugs mailing list
ubuntu-
Confirming due to a number of duplicates as well as I had this issue
previously as well and thought it had been fixed.
** Changed in: kde-systemsettings (Ubuntu)
Importance: Medium => High
Status: Needs Info => Confirmed
--
systemsettings doesn't load Display, Disk and Filesystems cont
Can anyone else confirm the fix?
--
systemsettings doesn't load Display, Disk and Filesystems control module
https://launchpad.net/bugs/38692
--
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
With Edgy/Kubuntu the original load did not have this problem.
It appeared on all 4 of my systems after an update in the middle of January.
The problem appeared "universal" so I did not attempt reporting a problem,
assuming a fix would be forthcoming.
I update my systems at least once a week and
I still have the same problem.
Is there any workaround here?
There is settings window snapshot in attachment.
$ sudo kcmshell displayconfig
Password:
X Error: BadDevice, invalid or uninitialized input device 169
Major opcode: 145
Minor opcode: 3
Resource id: 0x0
Failed to open device
X Er
@prokher: Your problem is a different issue. Use "kdesu kcmshell
displayconfig" or "kdesu displayconfig", either should work.
--
systemsettings doesn't load Display, Disk and Filesystems control module
https://bugs.launchpad.net/bugs/38692
You received this bug notification because you are a memb
$ kdesu displayconfig
X Error: BadDevice, invalid or uninitialized input device 169
Major opcode: 145
Minor opcode: 3
Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 169
Major opcode: 145
Minor opcode: 3
Resource id: 0x0
Failed to o
Has anyone observed the problem on Hardy?
--
systemsettings doesn't load Display, Disk and Filesystems control module
https://bugs.launchpad.net/bugs/38692
You received this bug notification because you are a member of Kubuntu
Team, which is a direct subscriber.
--
kubuntu-bugs mailing list
[EM
I have had this bug in Feisty and still have it in Gutsy.
OUTPUT--
[EMAIL PROTECTED]:~$ kcmshell displayconfig
Pythonize constructor -- pid = 5315
Python interpreter initialized!
Pythonize constructor -- pid = 5315
open /dev/mem: Permission denied
VESA BIOS Extensions n
This bug happened to me soon after installing Kubuntu 7.10 on what was
previously a Windows only box. System is dual monitor. The module
stopped working a few steps after after I had successfully enabled the
second monitor. The monitor first came up as a generic with only 640x480
available, so I re
I just started seeing a similar problem, but my output of "$ kcmshell
displayconfig" is a bit different:
$ kcmshell displayconfig
Pythonize constructor -- pid = 11128
Python interpreter initialized!
Pythonize constructor -- pid = 11128
open /dev/mem: Permission denied
VESA BIOS Extensions not de
This bug has reappeared after updating Edgy on Sept. 30, 2006. The beta
was fine, but after updating, these modules no longer work, either from
kde-systemsettings or from kcontrol. I haven't tried "kcmshell
displayconfig" from the command line, but will do so tonight when I am
at home.
--
systems
I could confirm this bug before. However, the modules all seem to be
loading fine for me now...
** Bug 63546 has been marked a duplicate of this bug
--
systemsettings doesn't load Display, Disk and Filesystems control module
https://launchpad.net/bugs/38692
--
ubuntu-bugs mailing list
ubuntu-
With Hardy Release: happens for "Disk and Filesystems" and "User
management" modules if they are opened after opening "Printers" module
Steps to reproduce:
1) open "System Settings" or run systemsettings in konsole
2) open "Printers" and press the back button to go back
3) open "Disk and Filesyste
confirming
--
systemsettings doesn't load Display, Disk and Filesystems control module
https://bugs.launchpad.net/bugs/38692
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https:/
Has happened to me with Disk and Filesystems on Hardy RC. I had rebooted after
doing the update from Gutsy to Hardy RC and was opening all the System settings
one by one to look at any new features and the Disk and Filesystems module
failed to load. However after i closed and reopened System set
** Changed in: kde-guidance (Ubuntu)
Sourcepackagename: kde-systemsettings => kde-guidance
** Changed in: kde-guidance (Ubuntu)
Assignee: Kubuntu Bugs (kubuntu-bugs) => (unassigned)
--
systemsettings doesn't load Display, Disk and Filesystems control module
https://bugs.launchpad.net/bugs/3
Has anyone observed the problem on Hardy?
--
systemsettings doesn't load Display, Disk and Filesystems control module
https://bugs.launchpad.net/bugs/38692
You received this bug notification because you are a member of Kubuntu
Team, which is a direct subscriber.
--
kubuntu-bugs mailing list
[EM
This bug happened to me soon after installing Kubuntu 7.10 on what was
previously a Windows only box. System is dual monitor. The module
stopped working a few steps after after I had successfully enabled the
second monitor. The monitor first came up as a generic with only 640x480
available, so I re
Yes, I'm experiencing this in hardy
I tried displayconfig and kcmshell displayconfig but this didn't work
(using radeonhd, if it matters)
--
systemsettings doesn't load Display, Disk and Filesystems control module
https://bugs.launchpad.net/bugs/38692
You received this bug notification because y
I just started seeing a similar problem, but my output of "$ kcmshell
displayconfig" is a bit different:
$ kcmshell displayconfig
Pythonize constructor -- pid = 11128
Python interpreter initialized!
Pythonize constructor -- pid = 11128
open /dev/mem: Permission denied
VESA BIOS Extensions not de
This bug has reappeared after updating Edgy on Sept. 30, 2006. The beta
was fine, but after updating, these modules no longer work, either from
kde-systemsettings or from kcontrol. I haven't tried "kcmshell
displayconfig" from the command line, but will do so tonight when I am
at home.
--
systems
I could confirm this bug before. However, the modules all seem to be
loading fine for me now...
** Bug 63546 has been marked a duplicate of this bug
--
systemsettings doesn't load Display, Disk and Filesystems control module
https://launchpad.net/bugs/38692
--
ubuntu-bugs mailing list
ubuntu-
** Changed in: kde-guidance (Ubuntu)
Sourcepackagename: kde-systemsettings => kde-guidance
** Changed in: kde-guidance (Ubuntu)
Assignee: Kubuntu Bugs (kubuntu-bugs) => (unassigned)
--
systemsettings doesn't load Display, Disk and Filesystems control module
https://bugs.launchpad.net/bugs/3
Confirming due to a number of duplicates as well as I had this issue
previously as well and thought it had been fixed.
** Changed in: kde-systemsettings (Ubuntu)
Importance: Medium => High
Status: Needs Info => Confirmed
--
systemsettings doesn't load Display, Disk and Filesystems cont
Can anyone else confirm the fix?
--
systemsettings doesn't load Display, Disk and Filesystems control module
https://launchpad.net/bugs/38692
--
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
With Edgy/Kubuntu the original load did not have this problem.
It appeared on all 4 of my systems after an update in the middle of January.
The problem appeared "universal" so I did not attempt reporting a problem,
assuming a fix would be forthcoming.
I update my systems at least once a week and
I have had this bug in Feisty and still have it in Gutsy.
OUTPUT--
[EMAIL PROTECTED]:~$ kcmshell displayconfig
Pythonize constructor -- pid = 5315
Python interpreter initialized!
Pythonize constructor -- pid = 5315
open /dev/mem: Permission denied
VESA BIOS Extensions n
I still have the same problem.
Is there any workaround here?
There is settings window snapshot in attachment.
$ sudo kcmshell displayconfig
Password:
X Error: BadDevice, invalid or uninitialized input device 169
Major opcode: 145
Minor opcode: 3
Resource id: 0x0
Failed to open device
X Er
@prokher: Your problem is a different issue. Use "kdesu kcmshell
displayconfig" or "kdesu displayconfig", either should work.
--
systemsettings doesn't load Display, Disk and Filesystems control module
https://bugs.launchpad.net/bugs/38692
You received this bug notification because you are a memb
$ kdesu displayconfig
X Error: BadDevice, invalid or uninitialized input device 169
Major opcode: 145
Minor opcode: 3
Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 169
Major opcode: 145
Minor opcode: 3
Resource id: 0x0
Failed to o
With Hardy Release: happens for "Disk and Filesystems" and "User
management" modules if they are opened after opening "Printers" module
Steps to reproduce:
1) open "System Settings" or run systemsettings in konsole
2) open "Printers" and press the back button to go back
3) open "Disk and Filesyste
confirming
--
systemsettings doesn't load Display, Disk and Filesystems control module
https://bugs.launchpad.net/bugs/38692
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https:/
Has happened to me with Disk and Filesystems on Hardy RC. I had rebooted after
doing the update from Gutsy to Hardy RC and was opening all the System settings
one by one to look at any new features and the Disk and Filesystems module
failed to load. However after i closed and reopened System set
Yes, I'm experiencing this in hardy
I tried displayconfig and kcmshell displayconfig but this didn't work
(using radeonhd, if it matters)
--
systemsettings doesn't load Display, Disk and Filesystems control module
https://bugs.launchpad.net/bugs/38692
You received this bug notification because y
I still have the same problem.
Is there any workaround here?
There is settings window snapshot in attachment.
$ sudo kcmshell displayconfig
Password:
X Error: BadDevice, invalid or uninitialized input device 169
Major opcode: 145
Minor opcode: 3
Resource id: 0x0
Failed to open device
X Er
@prokher: Your problem is a different issue. Use "kdesu kcmshell
displayconfig" or "kdesu displayconfig", either should work.
--
systemsettings doesn't load Display, Disk and Filesystems control module
https://bugs.launchpad.net/bugs/38692
You received this bug notification because you are a memb
1 - 100 of 108 matches
Mail list logo
